NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Apache Tomcat Vulnerable to Relative Path TraversalGHSA-wmwf-9ccg-fff5

HIGHFix: apache/tomcat@130d36d

GHSA-wmwf-9ccg-fff5 is a high-severity (CVSS 7.5) CWE-23 vulnerability in org.apache.tomcat:tomcat. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Also known asBIT-tomcat-2025-55752CVE-2025-55752
Published
Updated
Affected
12 pkgs
Patched
9 / 12
Exploits
2 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wmwf-9ccg-fff5.

EPSS Exploitation Probability

via FIRST.org ↗
64.4%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
0.00%28.8%57.6%86.5%0.1%64.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

12 pkgs affected
☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina+4 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

12 total 9 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 11.0.0-M1&&< 11.0.1111.0.11org.apache.tomcat:tomcat:11.0.11
☕Mavenorg.apache.tomcat:tomcat≥ 10.1.0-M1&&< 10.1.4510.1.45org.apache.tomcat:tomcat:10.1.45
☕Mavenorg.apache.tomcat:tomcat≥ 9.0.0-M11&&< 9.0.1099.0.109org.apache.tomcat:tomcat:9.0.109
☕Mavenorg.apache.tomcat:tomcat≥ 8.5.6No fix
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 11.0.0-M1&&< 11.0.1111.0.11org.apache.tomcat:tomcat-catalina:11.0.11
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 10.1.0-M1&&< 10.1.4510.1.45org.apache.tomcat:tomcat-catalina:10.1.45

Affected Products

1 product · 23 configurations
Application
tomcatapache
≥ 11.0.0 && ≤ 8.5.100
1 version
9.0.0
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

masahiro331/CVE-2025-55752

⭐ 14🍴 3Apr 2026

TAM-K592/CVE-2025-55752

CVE-2025-55752, Apache Tomcat that allows directory traversal via URL re

⭐ 13🍴 2Feb 2026

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.tomcat:tomcat to 11.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmwf-9ccg-fff5 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as Important rather than Critical because successful exploitation depends on specific, non-default configuration conditions. The flaw only becomes exploitable when both URL rewriting rules that modify the request path are in use and HTTP PUT requests are enabled — a feature typically…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. To reduced the risk, by disabling or strictly limiting the use of HTTP PUT requests to trusted, authenticated users only. Additionally, administrators should review and adjust URL rewrite rules to ensure they do not manipulate request paths in ways that could expose protected directories such as /WEB-INF/ or /META-INF/. Implementing strict access controls and monitoring for unexpected rewrite or upload behavior can further minimize potential exploitation.
Source: Red Hat security advisory for GHSA-wmwf-9ccg-fff5 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10tomcat-1:10.1.36-3.el10_1.1RHSA-2025:23050
Red Hat Enterprise Linux 10tomcat9-1:9.0.87-8.el10_1.1RHSA-2025:23052
Red Hat Enterprise Linux 10.0 Extended Update Supporttomcat-1:10.1.36-1.el10_0.3RHSA-2025:23051
Red Hat Enterprise Linux 10.0 Extended Update Supporttomcat9-1:9.0.87-5.el10_0.4RHSA-2025:23053
Red Hat Enterprise Linux 8tomcat-1:9.0.87-1.el8_10.7RHSA-2025:23048
Red Hat Enterprise Linux 8.2 Advanced Update Supportpki-deps:10.6-8020020260128173505.4cda2c84RHSA-2026:2725
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportpki-deps:10.6-8040020260129154709.522a0ee4RHSA-2026:2724
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportpki-deps:10.6-8060020260128101437.ad008a3aRHSA-2026:2726

Frequently Asked Questions

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 manip
O3 Security · Impact-Aware SCA

Is GHSA-wmwf-9ccg-fff5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache Tomcat Vulnerable to Relative Path Traversal