Apache · Apache Tomcat · CWE-44 · CWE-502 · published 2025-03-10
CVE-2025-24813Apache Tomcat Path Equivalence Vulnerability
Patch today Known exploited server software, total technical impact.
CVE-2025-24813 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-04-01. EPSS estimates a 99.9% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This Apache Tomcat vulnerability: CVSS 10.0 (v3.1), a successful attack gives total control of the component. Patched packages are out for Debian and Red Hat Enterprise Linux. US federal agencies must remediate by 2025-04-22. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (federal due date 2025-04-22)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | tomcat10 | Fixed in 10.1.35-1 |
| 13 trixie | tomcat9 | Fixed in 9.0.70-2 | |
| 12 bookworm | tomcat10 | Fixed in 10.1.34-0+deb12u2 | |
| 12 bookworm | tomcat9 | Fixed in 9.0.70-2 | |
| Red Hat Enterprise Linux (+7 more packages) | RHEL 10 | tomcat9 | Fixed in 9.0.87-5.el10_0 RHSA-2025:7494 |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
App serverApache Tomcat
Path EquivalenceCVE-2025-24813
Why: Known exploited server software, total technical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2025-04-01 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 100% (100th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 10.0 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-44: Path Equivalence: 'file.name' (Internal Dot) · CWE-502: Deserialization of Untrusted Data
More from this vendor: all Apache vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Apache Software Foundation Apache Tomcat
11.0.0-M1through11.0.2(affected)10.1.0-M1through10.1.34(affected)9.0.0.M1through9.0.98(affected)8.5.0through8.5.100(affected)3to before8.5.0(unknown)10.0.0-M1through10.0.27(unknown)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.