dbcve.org
TomcatWeb server / proxy · Apache

CVE-2025-55752

HIGH · 7.5 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 →
81/100
Remediation priority · High
High EPSS Public exploit Remotely reachable Zero-click

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
Relative Path Traversal vulnerability in Apache Tomcat. The fix for bug 60013 introduced a regression where the rewritten URL was normalized before it was decoded. This introduced the possibility that, for rewrite rules that rewrite query parameters to the URL, an attacker could manipulate the request URI to bypass security constraints including the protection for /WEB-INF/ and /META-INF/. If PUT requests were also enabled then malicious files could be uploaded leading to remote code execution. PUT requests are normally limited to trusted users and it is considered unlikely that PUT requests would be enabled in conjunction with a rewrite that manipulated the URI. 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.0.M11 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.6 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

A detailed technical summary for this CVE is being prepared.

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.6, <= 8.5.100>= 9.0.1, < 9.0.109>= 10.0.0, < 10.0.27>= 10.1.0, < 10.1.45>= 11.0.0, < 11.0.11= 9.0.0

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
Recommended fix High confidence

Tomcat 8.5.x: upgrade to 8.5.101+ (if available) or migrate to 9.0.109+; Tomcat 9.0.x: upgrade to 9.0.109; Tomcat 10.1.x: upgrade to 10.1.45; Tomcat 11.x: upgrade to 11.0.11

  1. 1. Identify the currently installed Apache Tomcat version by checking the $CATALINA_HOME/lib/catalina.jar manifest or using the version.sh script
  2. 2. Download the appropriate fixed Tomcat version for your major release branch (see upgrade_path)
  3. 3. Stop the Tomcat service/application
  4. 4. Back up the current Tomcat installation directory including conf/ and webapps/
  5. 5. Extract the new Tomcat version to the same location, preserving your existing conf/server.xml and conf/context.xml configurations
  6. 6. Restore any custom configuration files from the backup (ensure context.xml and any rewrite rules are preserved)
  7. 7. Start the Tomcat service
  8. 8. Verify the application functions correctly and test that the vulnerability is mitigated
Caveat Minor: Ensure custom rewrite rules (rewrite.config) still function correctly after upgrade as URL handling behavior changed; ensure any third-party Tomcat extensions are compatible with the new version

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55752 — 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-55752 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