In short
Apache Tomcat has a critical vulnerability in its file upload feature that can allow attackers to read sensitive files, modify uploaded content, or run malicious code on the server if certain features are enabled. This happens because the server doesn't properly validate file paths when handling partial uploads.
Technical detail
CVE-2025-24813 exploits path equivalence via dot-based naming in partial PUT requests to the default servlet. With writes enabled and partial PUT support active, attackers can traverse to sensitive file directories, read/modify files, or achieve RCE through deserialization when file-based session persistence is configured. The vulnerability affects Tomcat 9.0.0–9.0.98, 10.1.0–10.1.34, and 11.0.0–11.0.2.
Summary generated and translated by AI from the official description.
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.
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.