Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2025-55754: Apache Tomcat: console manipulation via escape sequences in log messages

Noroxi assessment

Priority: Plan (action score 41/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 10.1% (FIRST EPSS); higher than 95.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: Apache Software Foundation Apache Tomcat 11.0.11.

Add it to your regular patch cycle. Upgrade to Apache Software Foundation Apache Tomcat 11.0.11 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. Tomcat did not escape ANSI escape sequences in log messages. If Tomcat was running in a console on a Windows operating system, and the console supported ANSI escape sequences, it was possible for an attacker to use a specially crafted URL to inject ANSI escape sequences to manipulate the console and the clipboard and attempt to trick an administrator into running an attacker controlled command. While no attack vector was found, it may have been possible to mount this attack on other operating systems. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.40 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.60 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue.

CriticalCVSS 9.6 · v3.1—No exploit Fix available
Published
Oct 27, 2025
Updated
Oct 8, 2026
EPSS
10.1% · 95th percentile

Report tools

JSON

Action score

41

Plan

Add it to your regular patch cycle.

CVSS
38 / 40 · 9.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 10.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-55754

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for apache records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachetomcat

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache tomcat8.5.60 and later · up to 8.5.100 inclusive
  • apache tomcat9.0.40 and later · before 9.0.109
  • apache tomcat10.0.0 and later · before 10.0.27
  • apache tomcat10.1.0 and later · before 10.1.45
  • apache tomcat11.0.0 and later · before 11.0.11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Tomcat

    • 11.0.0-M1 and later · up to and including 11.0.10affected · semver
    • 10.1.0-M1 and later · up to and including 10.1.44affected · semver
    • 9.0.40 and later · up to and including 9.0.108affected · semver
    • 8.5.60 and later · up to and including 8.5.100affected · semver
    • 3 and later · before 8.5.0unknown · semver
    • 10.0.0-M1 and later · up to and including 10.0.27unknown · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11tomcat9before 9.0.107-0+deb11u29.0.107-0+deb11u2
Debian:12tomcat10before 10.1.52-1~deb12u110.1.52-1~deb12u1
Debian:12tomcat9before 9.0.70-29.0.70-2
Debian:13tomcat10before 10.1.52-1~deb13u110.1.52-1~deb13u1
Debian:13tomcat11before 11.0.15-1~deb13u111.0.15-1~deb13u1
Debian:14tomcat10before 10.1.46-110.1.46-1
Debian:14tomcat11before 11.0.11-111.0.11-1
Mavenorg.apache.tomcat:tomcatfrom 10.1.0-M1 · before 10.1.4510.1.45
Mavenorg.apache.tomcat:tomcatfrom 11.0.0-M1 · before 11.0.1111.0.11
Mavenorg.apache.tomcat:tomcatfrom 8.5.60 · up to and including 8.5.100—
Mavenorg.apache.tomcat:tomcatfrom 9.0.40 · before 9.0.1099.0.109
Mavenorg.apache.tomcat:tomcat-catalinafrom 10.1.0-M1 · before 10.1.4510.1.45
Mavenorg.apache.tomcat:tomcat-catalinafrom 11.0.0-M1 · before 11.0.1111.0.11
Mavenorg.apache.tomcat:tomcat-catalinafrom 8.5.60 · up to and including 8.5.100—
Mavenorg.apache.tomcat:tomcat-catalinafrom 9.0.40 · before 9.0.1099.0.109
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 10.1.0-M1 · before 10.1.4510.1.45
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 11.0.0-M1 · before 11.0.1111.0.11
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 8.5.60 · up to and including 8.5.100—
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 9.0.40 · before 9.0.1099.0.109
openSUSE:Leap 15.6tomcatbefore 9.0.111-150200.96.19.0.111-150200.96.1
openSUSE:Leap 15.6tomcat10before 10.1.48-150200.5.54.110.1.48-150200.5.54.1
openSUSE:Leap 15.6tomcat11before 11.0.13-150600.13.12.111.0.13-150600.13.12.1
openSUSE:Leap 16.0tomcatbefore 9.0.111-160000.1.19.0.111-160000.1.1
openSUSE:Leap 16.0tomcat10before 10.1.52-160000.1.110.1.52-160000.1.1

+96

Same product

apache: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV
    99Now
  • CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x beforeKEV
    96Now
  • CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV
    92Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-55668Aug 13, 2025 · Apache Tomcat: session fixation via rewrite valve
    26Monitor
  • ← EarlierCVE-2025-55752Oct 27, 2025 · Apache Tomcat: Directory traversal via rewrite with possible RCE if PUT is enabled
    49Plan
  • Later →CVE-2025-61795Oct 27, 2025 · Apache Tomcat: Delayed cleaning of multi-part upload temporary files may lead to DoS
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Tomcat11.0.11 · descriptionVendor (CNA)
debian:tomcat1010.1.52-1~deb12u1 · Debian:12Package registry (OSV)
debian:tomcat1111.0.15-1~deb13u1 · Debian:13Package registry (OSV)
debian:tomcat99.0.70-2 · Debian:12Package registry (OSV)
Maven:org.apache.tomcat:tomcat10.1.45Package registry (OSV)
Maven:org.apache.tomcat:tomcat11.0.11Package registry (OSV)
Maven:org.apache.tomcat:tomcat9.0.109Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina10.1.45Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina11.0.11Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina9.0.109Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core10.1.45Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core11.0.11Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core9.0.109Package registry (OSV)
opensuse:tomcat9.0.111-150200.96.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:tomcat1010.1.48-150200.5.54.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:tomcat1111.0.13-150600.13.12.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:tomcat1:10.1.49-1.el10 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat-admin-webapps1:10.1.49-1.el10 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat-docs-webapp1:10.1.49-1.el10 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat-el-5.0-api1:10.1.49-1.el10 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat91:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-admin-webapps1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-docs-webapp1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-el-3.0-api1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-jsp-2.3-api1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-lib1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-servlet-4.0-api1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:tomcat9-webapps1:9.0.110-2.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:tomcat1:10.1.49-1.el10_2.1 · Rocky Linux:10Package registry (OSV)
suse:tomcat9.0.111-150200.96.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP6Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-150 · Improper Neutralization of Escape, Meta, or Control Sequences

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records