CVE-2025-55752

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.

CVE-2025-55752 has a CVSS score of 7.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.0.11, 10.1.45, 9.0.109); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-55752? CVE-2025-55752 is a high-severity security vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 11.0.0-M1, < 11.0.11. It is fixed in 11.0.11, 10.1.45, 9.0.109.
2. How severe is CVE-2025-55752? CVE-2025-55752 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-55752?
   • org.apache.tomcat:tomcat (maven) (versions >= 11.0.0-M1, < 11.0.11)
   • org.apache.tomcat:tomcat-catalina (maven) (versions >= 11.0.0-M1, < 11.0.11)
   • org.apache.tomcat.embed:tomcat-embed-core (maven) (versions >= 11.0.0-M1, < 11.0.11)
4. Is there a fix for CVE-2025-55752? Yes. CVE-2025-55752 is fixed in 11.0.11, 10.1.45, 9.0.109. Upgrade to this version or later.
5. Is CVE-2025-55752 exploitable, and should I be worried? Whether CVE-2025-55752 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-55752 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-55752?
   • Upgrade org.apache.tomcat:tomcat to 11.0.11 or later
   • Upgrade org.apache.tomcat:tomcat to 10.1.45 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 11.0.11 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 10.1.45 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 11.0.11 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 10.1.45 or later
   • Upgrade org.apache.tomcat:tomcat to 9.0.109 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 9.0.109 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.109 or later