CVE-2025-24813: Apache Tomcat Path Equivalence
Apache Tomcat · listed in the CISA catalog of actively exploited vulnerabilities since 2025-04-01.
- CVSS v3.1 (CVE record)
- 10.0
- critical
- EPSS (exploit probability, 30 days)
- 99.9%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2025-04-01
- US federal due date 2025-04-22
- Ubuntu priority
- high
CVE-2025-24813 explained
CVE-2025-24813 is a path equivalence flaw in the Apache Tomcat Default Servlet involving internal dots in file names. When writes are enabled for the Default Servlet, it can lead to remote code execution, disclosure of sensitive files, or injection of content into uploaded files. It is listed in the CISA Known Exploited Vulnerabilities catalog.
Impact
A remote, unauthenticated attacker can view or inject content into security sensitive files. This requires Default Servlet writes enabled (off by default), partial PUT enabled (on by default), and a specific upload directory layout. Remote code execution is possible if the application also uses Tomcat's file based session persistence with the default storage location and includes a library usable in a deserialization attack. Confidentiality, integrity and availability impacts are all high.
Who is affected
Debian 12 (bookworm) tomcat10 is fixed in 10.1.34-0+deb12u2. On Ubuntu, tomcat9 fixes exist for 18.04 LTS (9.0.16-3ubuntu0.18.04.2+esm6), 20.04 LTS (9.0.31-1ubuntu0.9+esm1), 22.04 LTS (9.0.58-1ubuntu0.2+esm2) and 24.04 LTS (9.0.70-2ubuntu0.1+esm1), all through Ubuntu Pro (ESM). Ubuntu 24.04 LTS tomcat10 is fixed in 10.1.16-1ubuntu0.1~esm1 via Ubuntu Pro (ESM). Ubuntu 25.10 tomcat9 is fixed in 9.0.70-2ubuntu2, but that release is end of life.
Written with AI from the data on this page and checked against it automatically.
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.
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.
CISA notes
- This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: lists.apache.org/thread/j5fkjv2k477os90nczf2v9l61fb0kkgq
- nvd.nist.gov/vuln/detail/CVE-2025-24813
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Apache Software Foundation Apache TomcatAffectedFixed in
- ≥ 8.5.0, ≤ 8.5.100
- ≥ 9.0.0.M1, ≤ 9.0.98
- ≥ 10.1.0-M1, ≤ 10.1.34
- ≥ 11.0.0-M1, ≤ 11.0.2
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software Foundation Apache Tomcat |
| not stated |
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 25.10·tomcat9
end of life
Fixed: 9.0.70-2ubuntu2
Ubuntu 24.04 LTS·tomcat10
fix via Ubuntu Pro
Fixed: 10.1.16-1ubuntu0.1~esm1
Ubuntu 24.04 LTS·tomcat9
fix via Ubuntu Pro
Fixed: 9.0.70-2ubuntu0.1+esm1
Ubuntu 22.04 LTS·tomcat9
fix via Ubuntu Pro
Fixed: 9.0.58-1ubuntu0.2+esm2
Ubuntu 20.04 LTS·tomcat9
fix via Ubuntu Pro
Fixed: 9.0.31-1ubuntu0.9+esm1
Ubuntu 18.04 LTS·tomcat9
fix via Ubuntu Pro
Fixed: 9.0.16-3ubuntu0.18.04.2+esm6
Debian 12 (bookworm)·tomcat10
Fixed: 10.1.34-0+deb12u2
What to do
- Identify hosts running the
tomcat9ortomcat10packages. - On Debian 12, update
tomcat10to10.1.34-0+deb12u2or later. - On Ubuntu 18.04, 20.04, 22.04 and 24.04 LTS, enable Ubuntu Pro (ESM) and install the fixed Tomcat packages.
- Restart Tomcat after updating so the fixed code is loaded.
- Check that writes for the Default Servlet stay disabled unless strictly required.
- Upgrade Ubuntu 25.10 systems to a supported release, since it is end of life.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace tomcat9 with the source package from the table above (this CVE affects 2 source packages).
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="tomcat9"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="tomcat9"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-44 Path Equivalence: 'file.name' (Internal Dot), CWE-502 Deserialization of Untrusted Data
Questions about CVE-2025-24813
- Is a default Tomcat installation vulnerable?
- Exploitation requires writes to be enabled for the Default Servlet, which is disabled by default. Partial PUT support is enabled by default. Remote code execution additionally needs file based session persistence with the default storage location and a library usable in a deserialization attack.
- Do I need Ubuntu Pro to get the fix?
- On Ubuntu 18.04, 20.04, 22.04 and 24.04 LTS, the fixed
tomcat9andtomcat10packages are published only through Ubuntu Pro (ESM). Debian 12 receives the fix through the standard archive. - Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-04-01, with a US federal due date of 2025-04-22. Known ransomware use is listed as unknown.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.