CVE Intelligence
High File handling exploit reference

CVE-2025-55752 — Apache Tomcat: Directory traversal via rewrite with possible RCE if PUT is enabled

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.

Published Oct 27, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: apache

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 64.4% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
64.41%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Apache Software Foundation
Tomcat
CVSS base
7.5
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented mitigation — www.vicarius.io (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Tomcat).
  2. Apply the documented mitigations until a definitive fix is available.
  3. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  4. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Tomcat version 9.0.0-milestone18version 9.0.0-milestone27version 9.0.0-milestone26version 9.0.0-milestone25version 9.0.0-milestone24version 9.0.0-milestone23version 9.0.0-milestone22version 9.0.0-milestone21
and 15 more version 9.0.0-milestone20version 9.0.0-milestone19≥ 8.5.6 and ≤ 8.5.100version 9.0.0-milestone17version 9.0.0-milestone16version 9.0.0-milestone15version 9.0.0-milestone14version 9.0.0-milestone13version 9.0.0-milestone12version 9.0.0-milestone11version 9.0.0≥ 11.0.0 and < 11.0.11≥ 10.1.0 and < 10.1.45≥ 10.0.0 and < 10.0.27≥ 9.0.1 and < 9.0.109
Vulnerable NIST National Vulnerability Database
Apache Software Foundation Tomcat ≥ 8.5.6 and ≤ 8.5.100≥ 9.0.0.M11 and ≤ 9.0.108≥ 10.1.0-M1 and ≤ 10.1.44≥ 11.0.0-M1 and ≤ 11.0.10 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 1.6 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-23 · Relative Path Traversal

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 64.41%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor file creation in web directories and paths with traversal sequences (../).
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · apache software foundation/apache tomcat
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2025
  • CVE published
    Oct 27, 2025 · apache

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
File handling
same class
CWE-23
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-55956 Apache Tomcat: Security constraints for default servlet ignored method Jun 29, 2026
  • CVE-2026-55276 Apache Tomcat: Logged effective web.xml is incomplete Jun 29, 2026
  • CVE-2026-55955 Apache Tomcat: EncryptInterceptor not protected against replay attacks Jun 29, 2026
  • CVE-2026-55957 Apache Tomcat: Authentication bypass with JNDIRealm and GSSAPI authenticated bind Jun 29, 2026
  • CVE-2026-50229 Apache Tomcat: XSS in number guess example Jun 29, 2026
  • CVE-2026-53404 Apache Tomcat: Bad ornext processing in RewriteValve Jun 29, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-55752 is "Apache Tomcat: Directory traversal via rewrite with possible RCE if PUT is enabled", rated High. It affects Tomcat (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 64.41% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.