This unauthenticated remote code execution vulnerability in Apache Tomcat’s partial PUT feature disclosed on March 10.
Exploit code for this vulnerability is publicly available and there is no authentication required to launch an attack, making prompt mitigation essential. According to Apache, successful exploitation requires specific conditions and some of them may end up enabled by default.
FortiGuard Labs identified ongoing attack attempts aimed at exploiting the Apache Tomcat remote code execution vulnerability, CVE-2025-24813. If successful, attackers could gain access to sensitive security files, allowing them to view or inject arbitrary content and potentially execute code remotely.
CVE-2025-24813 is the case number for the vulnerability, which has a CVSS base score of 9.8.
Versions affected by the vulnerability include Apache Tomcat:
- 11.0.0-M1 to 11.0.2
- 10.1.0-M1 to 10.1.34
- 9.0.0.M1 to 9.0.98
The original implementation of partial PUT used a temporary file based on the user provided file name and path with the path separator replaced by “.”.
If all of the following were true, a malicious user could 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 uploaded
- The security sensitive files also being uploaded via partial PUT
If all of the following were true, a malicious user could 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
In terms of a mitigation users of the affected versions should apply one of the following upgrades:
- Apache Tomcat 11.0.3 or later
- Apache Tomcat 10.1.35 or later
- Apache Tomcat 9.0.99 or later

