# CVE-2025-24813: Apache Tomcat Path Equivalence

> Attackers can exploit path equivalence in partial PUT requests to execute code or read sensitive files if default servlet writes are enabled.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 1 Apr 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2025
- **Updated:** 29 Oct 2025
- **Also known as:** ALSA-2025:7494, BIT-tomcat-2025-24813, CLSA-2025-1742577759, CLSA-2025-1742733084, CLSA-2025-1742737069, CLSA-2025-1750752721, CLSA-2025-1755272015, CLSA-2025-1755513827, CLSA-2025-1755516017, CLSA-2025-1760712981, DEBIAN-CVE-2025-24813, DLA-4108-1, DSA-5893-1, GHSA-83qj-6fr2-vhqg, RHSA-2025:3454, RHSA-2025:7494, RLSA-2025:7494, ROOT-APP-MAVEN-CVE-2025-24813, SUSE-SU-2025:0954-1, UBUNTU-CVE-2025-24813, USN-7525-1, USN-7525-2

## What is CVE-2025-24813?

CVE-2025-24813 is a critical path traversal vulnerability in Apache Tomcat, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-706 (Use of Incorrectly-Resolved Name or Reference), CWE-44 (Path Equivalence: 'file.name' (Internal Dot))

## Which versions are affected by CVE-2025-24813?

17 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, tomcat and org.apache.tomcat:tomcat-catalina. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.35 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.35 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.3 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.3 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 to 8.5.100 | None |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 to 8.5.100 | None |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.99 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.99 |
| `tomcat` | Bitnami | All versions | 9.0.99, 10.1.35, 11.0.3 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0-M1 | 10.1.35 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0-M1 | 10.1.35 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 11.0.0-M1 | 11.0.3 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 11.0.0-M1 | 11.0.3 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 to 8.5.100 | None |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 to 8.5.100 | None |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.99 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.99 |
| `tomcat9` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-admin-webapps` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-docs-webapp` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-el-3.0-api` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-jsp-2.3-api` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-lib` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-servlet-4.0-api` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-webapps` | AlmaLinux:10 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-admin-webapps` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-docs-webapp` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-el-3.0-api` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-jsp-2.3-api` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-lib` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-servlet-4.0-api` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `tomcat9-webapps` | Red Hat:enterprise_linux:10.0 | All versions | 1:9.0.87-5.el10_0 |
| `jws5-tomcat` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |
| `jws5-tomcat-admin-webapps` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |
| `jws5-tomcat-docs-webapp` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |
| `jws5-tomcat-el-3.0-api` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |
| `jws5-tomcat-java-jdk11` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |
| `jws5-tomcat-java-jdk8` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |
| `jws5-tomcat-javadoc` | Red Hat:jboss_enterprise_web_server:5.8::el7 | All versions | 0:9.0.87-8.redhat_00008.1.el7jws |

Products: Apache Tomcat, Debian Debian Linux, Netapp Bootstrap Os.

## How do I fix CVE-2025-24813?

Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 10.1.35, 11.0.3 or 9.0.99. US federal agencies must fix it by 22 Apr 2025.

## Is CVE-2025-24813 being exploited?

Yes. Attackers have exploited CVE-2025-24813 in the wild since at least 1 Apr 2025.

Public exploit code:

- his repository contains an automated Proof of Concept (PoC) script for exploiting **CVE-2025-24813**, a Remote Code Execution (RCE) vulnerability in Apache Tomcat. The vulnerability allows an attacker to upload a malicious serialized payload to the server, leading to arbitrary code execution via deserialization when specific conditions are met. (github_poc): https://github.com/absholi7ly/POC-CVE-2025-24813
- Apache Tomcat 远程代码执行漏洞批量检测脚本(CVE-2025-24813) (github_poc): https://github.com/iSee857/CVE-2025-24813-PoC
- Apache (CVE-2025-24813) GOExploiter Checker & Exploiter very Fast  (github_poc): https://github.com/drcrypterdotru/Apache-GOExploiter
- Apache Tomcat - Remote Code Execution via Session Deserialization (CVE-2025-24813) (github_poc): https://github.com/mbanyamer/Apache-Tomcat---Remote-Code-Execution-via-Session-Deserialization-CVE-2025-24813-
- CVE-2025-24813利用工具 (github_poc): https://github.com/charis3306/CVE-2025-24813
- cve-2025-24813验证脚本 (github_poc): https://github.com/qzy0x/cve-2025-24813_poc

## Other vulnerabilities in Apache Tomcat

- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)
- [CVE-2026-65637](https://insights.sbomify.com/CVE-2026-65637/): Apache Tomcat: HTTP/2 no-authority bypass of strict SNI validation - CVE-2026-32990 fix incomplete (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24813 and fix it if it is affected.

What it is: CVE-2025-24813 is a critical path traversal vulnerability in Apache Tomcat, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-24813 in the wild since at least 1 Apr 2025.

Affected packages and fixed versions:
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.35
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.35
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.3
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.3
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0 up to 8.5.100; no fix listed
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0 up to 8.5.100; no fix listed
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.99
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.99
- tomcat (Bitnami): affected all versions; fixed in 9.0.99, 10.1.35, 11.0.3
- org.apache.tomcat:tomcat-catalina (Maven): affected from 10.1.0-M1; fixed in 10.1.35
- org.apache.tomcat:tomcat-catalina (Maven): affected from 10.1.0-M1; fixed in 10.1.35
- org.apache.tomcat:tomcat-catalina (Maven): affected from 11.0.0-M1; fixed in 11.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24813/ (Markdown: https://insights.sbomify.com/CVE-2025-24813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24813
- OSV: https://osv.dev/vulnerability/CVE-2025-24813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24813/
Summaries are generated and may contain mistakes; the official description above is the record.