Back to Labs
Security Advisory

CVE-2025-24813

About

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.

Weakness (CWE):CWE-44CWE-502CWE-706

Rainforest analyst review

This is a path-equivalence flaw in Apache Tomcat's default servlet: an internal dot in a filename lets a request bypass naming protections. With writes enabled on the default servlet and partial PUT support on, an attacker can upload content that Tomcat treats as a different, sensitive file. Where the application uses Tomcat's file-based session persistence and includes a deserialization-capable library, the attacker can plant a serialized payload and have it deserialized, achieving remote code execution; a lesser configuration allows viewing or injecting into security-sensitive uploads.

Tomcat runs an enormous share of Java web applications, so even a bug gated behind specific settings has a large potential footprint, and a public proof of concept appeared within days, followed by exploitation attempts; it is on CISA's KEV list. The mitigating factor is that the dangerous configuration, default-servlet writes plus partial PUT plus file-based sessions plus a gadget-bearing library, is not the out-of-box default, so many instances are not exploitable. Upgrade to 11.0.3, 10.1.35, or 9.0.99. Short of patching, disable default-servlet write access and partial PUT, and confirm session persistence and classpath libraries do not line up into the RCE path.

References

Related CVEs

Frequently asked questions

What is 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.

How severe is CVE-2025-24813?

CVE-2025-24813 carries a CVSS 3.1 base score of 9.8, rated critical. On the Rainforest Risk Index — which weighs the severity alongside how easy the flaw is to reach and how broad its impact is — it scores 99 out of 100, in the critical band.

How is CVE-2025-24813 exploited?

According to the CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H): attack vector Network, attack complexity Low, privileges required None, user interaction None. Impact on confidentiality High, integrity High and availability High.

Which products are affected by CVE-2025-24813?

Public advisories list the following as affected: bootstrap os, debian linux, hci compute node, tomcat. Check the references on this page for the exact versions each vendor confirms.

How do I fix CVE-2025-24813?

Apply the fix the vendor published — the references on this page link to the primary advisories and patches. When patching can't happen right away, reduce the exposure of the affected component and watch it for exploitation attempts. Rainforest customers see this vulnerability correlated to their own assets and prioritized by real exposure, not by score alone.

Empower Your Security Strategy with Rainforest

Discover vulnerabilities early, prioritize critical threats, and protect what truly matters. Rainforest streamlines your security operations, saving you time and reducing costs, so you can focus on what drives your business forward.

Share this:LinkedInX Email