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

Published Oct 27, 2025
·
Updated

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.

Affected Software

38 affected componentsFixes available
Apache Tomcat>=11.0.0-M1, >=10.1.0-M1, >=9.0.0.M11
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0-M11<9.0.109
9.0.109
maven/org.apache.tomcat:tomcat-catalina>=9.0.0-M11<9.0.109
9.0.109
maven/org.apache.tomcat:tomcat>=9.0.0-M11<9.0.109
9.0.109
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.60<=8.5.100
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1<10.1.45
10.1.45
maven/org.apache.tomcat.embed:tomcat-embed-core>=11.0.0-M1<11.0.11
11.0.11
maven/org.apache.tomcat:tomcat-catalina>=8.5.60<=8.5.100
maven/org.apache.tomcat:tomcat-catalina>=10.1.0-M1<10.1.45
10.1.45
maven/org.apache.tomcat:tomcat-catalina>=11.0.0-M1<11.0.11
11.0.11
maven/org.apache.tomcat:tomcat>=8.5.60<=8.5.100
maven/org.apache.tomcat:tomcat>=10.1.0-M1<10.1.45
10.1.45
maven/org.apache.tomcat:tomcat>=11.0.0-M1<11.0.11
11.0.11
F5 Traffix SDC=5.2.0
Apache Tomcat>=8.5.6<=8.5.100
Apache Tomcat>=9.0.1<9.0.109
Apache Tomcat>=10.0.0<10.0.27
Apache Tomcat>=10.1.0<10.1.45
Apache Tomcat>=11.0.0<11.0.11
Apache Tomcat=9.0.0
Apache Tomcat=9.0.0-milestone11
Apache Tomcat=9.0.0-milestone12
Apache Tomcat=9.0.0-milestone13
Apache Tomcat=9.0.0-milestone14
Apache Tomcat=9.0.0-milestone15
Apache Tomcat=9.0.0-milestone16
Apache Tomcat=9.0.0-milestone17
Apache Tomcat=9.0.0-milestone18
Apache Tomcat=9.0.0-milestone19
Apache Tomcat=9.0.0-milestone20
Apache Tomcat=9.0.0-milestone21
Apache Tomcat=9.0.0-milestone22
Apache Tomcat=9.0.0-milestone23
Apache Tomcat=9.0.0-milestone24
Apache Tomcat=9.0.0-milestone25
Apache Tomcat=9.0.0-milestone26
Apache Tomcat=9.0.0-milestone27
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.109
  2. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 9.0.109
  3. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.109
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 10.1.45
  5. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 11.0.11
  6. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 10.1.45
  7. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 11.0.11
  8. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.45
  9. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.11
  10. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.11
  11. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.45
  12. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.109
  13. Compensating control

    If PUT requests are enabled, restrict PUT access to trusted users only (material notes PUT requests are normally limited to trusted users and that enabling PUT together with rewrite/URI manipulation can allow malicious file uploads leading to RCE).

Event History

Oct 27, 2025
CVE Published
via MITRE·05:29 PM
Data Sourced
via MITRE·05:29 PM
DescriptionWeakness
Data Sourced
via Red Hat·06:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
Affected Software
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionWeaknessAffected Software
Nov 14, 2025
Advisory Published
via F5·12:54 AM
Data Sourced
via F5·12:54 AM
DescriptionSeverityWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-55752?

CVE-2025-55752 is rated as a high-severity vulnerability due to its potential for exploitation through relative path traversal.

2

How do I fix CVE-2025-55752?

To fix CVE-2025-55752, upgrade your Apache Tomcat version to 11.0.11 or later, 10.1.45 or later, or 9.0.109 or later.

3

What versions of Apache Tomcat are affected by CVE-2025-55752?

CVE-2025-55752 affects Apache Tomcat versions from 11.0.0-M1 to 11.0.10, 10.1.0-M1 to 10.1.44, and 9.0.0.M11 to 9.0.108.

4

Can CVE-2025-55752 lead to data leakage?

Yes, CVE-2025-55752 can potentially allow attackers to access sensitive data by exploiting the relative path traversal vulnerability.

5

Is authentication required to exploit CVE-2025-55752?

No, CVE-2025-55752 can be exploited without authentication, making it particularly critical to patch.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203