dbcve.org
TomcatWeb server / proxy · Apache

CVE-2025-55754

CRITICAL · 9.6 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 9.0.109 / 10.0.27 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tomcat fails to escape ANSI escape sequences in log messages. When Tomcat runs on a Windows console supporting ANSI codes, a specially crafted URL can inject escape sequences that manipulate the console display and clipboard, potentially tricking administrators into executing attacker-controlled commands.

MitigationUpgrade to Apache Tomcat 11.0.11+, 10.1.45+, or 9.0.109+ (or 8.5.101+ if using 8.5.x) to patch the vulnerability. Alternatively, disable console logging or avoid running Tomcat in console mode on Windows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 8.5.60, <= 8.5.100>= 9.0.40, < 9.0.109>= 10.0.0, < 10.0.27>= 10.1.0, < 10.1.45>= 11.0.0, < 11.0.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Tomcat version
    Run the version.sh (Unix) or version.bat (Windows) script from the Tomcat bin directory, or check the startup logs for the version number at startup
    Affected if The installed version falls within any of these ranges: 8.5.60-8.5.100, 9.0.40-9.0.108, 10.0.0-10.0.26, 10.1.0-10.1.44, or 11.0.0-11.0.10
  2. Confirm Windows platform
    Check the operating system where Tomcat is running using 'systeminfo' or 'ver' command, or check the value of os.name system property
    Affected if Tomcat is running on Windows with a console that supports ANSI escape codes (Windows 10 build 1607+ or Windows Server 2016+ with ANSI support enabled)
  3. Verify console logging is enabled
    Examine the logging configuration files (conf/logging.properties) and check for ConsoleHandler or stdout handlers, or check if Tomcat is running in console mode (not installed as a Windows service)
    Affected if Console logging handlers are configured and Tomcat is running interactively in a Windows console window rather than solely as a service with file-based logging only

A user is affected if they are running a vulnerable Tomcat version on Windows with console logging enabled and the console supports ANSI codes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.109 / 10.0.27 / 10.1.45 or later
Fixed in 9.0.10910.0.2710.1.45
Interim mitigation

Upgrade to Apache Tomcat 11.0.11+, 10.1.45+, or 9.0.109+ (or 8.5.101+ if using 8.5.x) to patch the vulnerability. Alternatively, disable console logging or avoid running Tomcat in console mode on Windows.

Recommended fix High confidence

Tomcat 9.0.109+, 10.1.45+, or 11.0.11+ (depending on current branch)

  1. 1. Identify the currently running Apache Tomcat version using the version.sh script or server info page
  2. 2. For Tomcat 8.5.x (8.5.60-8.5.100): Upgrade to Tomcat 10.1.45+ or 11.0.11+ (8.5.x is EOL; migrate to a supported branch)
  3. 3. For Tomcat 9.0.x (9.0.40-9.0.108): Download and install Apache Tomcat 9.0.109 or later from https://tomcat.apache.org/
  4. 4. For Tomcat 10.0.x (10.0.0-10.0.26): Upgrade to Tomcat 10.1.45 or later from the 10.1 branch
  5. 5. For Tomcat 10.1.x (10.1.0-10.1.44): Download and install Apache Tomcat 10.1.45 or later
  6. 6. For Tomcat 11.0.x (11.0.0-M1-11.0.10): Upgrade to Apache Tomcat 11.0.11 or later
  7. 7. Stop the Tomcat service, replace the installation files, and restart Tomcat
  8. 8. Verify the upgrade by checking the version and ensuring ANSI escape sequences in logs are now properly escaped
Caveat Minor version upgrades within the same major branch typically have minimal breaking changes; however, review release notes for any configuration or behavioral changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55754 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55754 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data