CVE-2025-24813

Path Equivalence: 'file.Name' (Internal Dot) leading to Remote Code Execution and/or Information disclosure and/or malicious content added to uploaded files via write enabled Default Servlet in Apache Tomcat.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.2, from 10.1.0-M1 through 10.1.34, from 9.0.0.M1 through 9.0.98. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected.

If all of the following were true, a malicious user was able to view security sensitive files and/or inject content into those files:
- writes enabled for the default servlet (disabled by default)

• support for partial PUT (enabled by default)
• a target URL for security sensitive uploads that was a sub-directory of a target URL for public uploads
  - attacker knowledge of the names of security sensitive files being uploaded
  - the security sensitive files also being uploaded via partial PUT

If all of the following were true, a malicious user was able to perform remote code execution:

• writes enabled for the default servlet (disabled by default)
  - support for partial PUT (enabled by default)
  - application was using Tomcat's file based session persistence with the default storage location
  - application included a library that may be leveraged in a deserialization attack

Users are recommended to upgrade to version 11.0.3, 10.1.35 or 9.0.99, which fixes the issue.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2025-24813 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no 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.3, 10.1.35, 9.0.99); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-24813? CVE-2025-24813 is a critical-severity insecure deserialization vulnerability in org.apache.tomcat:tomcat-catalina (maven), affecting versions >= 11.0.0-M1, < 11.0.3. It is fixed in 11.0.3, 10.1.35, 9.0.99. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2025-24813? CVE-2025-24813 has a CVSS score of 9.8 (Critical). 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-24813?
   • org.apache.tomcat:tomcat-catalina (maven) (versions >= 11.0.0-M1, < 11.0.3)
   • org.apache.tomcat.embed:tomcat-embed-core (maven) (versions >= 11.0.0-M1, < 11.0.3)
4. Is there a fix for CVE-2025-24813? Yes. CVE-2025-24813 is fixed in 11.0.3, 10.1.35, 9.0.99. Upgrade to this version or later.
5. Is CVE-2025-24813 exploitable, and should I be worried? Whether CVE-2025-24813 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-24813 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-24813?
   • Upgrade org.apache.tomcat:tomcat-catalina to 11.0.3 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 10.1.35 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 9.0.99 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 11.0.3 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 10.1.35 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.99 or later