CVE-2025-24813criticalunder attackCWE-44CWE-502

CVE-2025-24813: critical vulnerability in Apache Tomcat

Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUT

Published · Updated

100Vexday Risk Score

Patch now. It under exploitation confirmed by CISA and has a working public exploit.

ssvc Actcvss 10epss 100%
from disclosure to weapon0 days
Published on NVDMar 10
1st PoCMay 27
metasploitMar 10
CISA KEV+22d
exploitation probability
100%top 1% of all CVEs
observed exploitation
yesCISA + VulnCheck
107 public exploit(s)
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Affected
1 product (11 components)
Red Hat Enterprise Linux 6
workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Fixed
13 products (122 components)
Red Hat Enterprise Linux AppStream (v. 10) · Red Hat JBoss Web Server 5.8 for RHEL 7 Server · Red Hat JBoss Web Server 5.8 for RHEL 8 · Red Hat JBoss Web Server 5.8 for RHEL 9 · Red Hat JBoss Web Server 6.1 for RHEL 8 · and others 8
Not affected
5 products (27 components) — because the vulnerable code is not present in the product
Red Hat Enterprise Linux 7 · Red Hat JBoss Web Server 6.1 for RHEL 8 · Red Hat JBoss Web Server 6.1 for RHEL 9 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 9
Action required by CISAfederal deadline: 2025-04-22

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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.

The full analysis of this CVE is available in Portuguese →

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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
public PoCs found — 107
exploitdbwww.exploit-db.com/exploits/52134unverifiedgithubgithub.com/absholi7ly/POC-CVE-2025-24813★ 197githubgithub.com/iSee857/CVE-2025-24813-PoC★ 97githubgithub.com/drcrypterdotru/Apache-GOExploiter★ 20githubgithub.com/mbanyamer/Apache-Tomcat---Remote-Code-Execution-via-Session-Deserialization-CVE-2025-24813-★ 19githubgithub.com/charis3306/CVE-2025-24813★ 16githubgithub.com/qzy0x/cve-2025-24813_poc★ 11githubgithub.com/x00byte/PutScanner★ 9githubgithub.com/Franconyu/Poc_for_CVE-2025-24813★ 9githubgithub.com/u238/Tomcat-CVE_2025_24813★ 7githubgithub.com/msadeghkarimi/CVE-2025-24813-Exploit★ 7githubgithub.com/Shivshantp/CVE-2025-24813★ 6githubgithub.com/Erosion2020/CVE-2025-24813-vulhub★ 5githubgithub.com/Mattb709/CVE-2025-24813-Scanner★ 5githubgithub.com/Alaatk/CVE-2025-24813-POC★ 5githubgithub.com/AsaL1n/CVE-2025-24813★ 4githubgithub.com/cchopin/CVE-Arsenal-Lab★ 4githubgithub.com/beyond-devsecops/CVE-2025-24813★ 4githubgithub.com/EQSTLab/CVE-2025-24813★ 3githubgithub.com/N0c1or/CVE-2025-24813_POC★ 3githubgithub.com/imbas007/CVE-2025-24813-apache-tomcat★ 3githubgithub.com/AlperenY-cs/CVE-2025-24813★ 3githubgithub.com/Mattb709/CVE-2025-24813-PoC-Apache-Tomcat-RCE★ 3githubgithub.com/yuzuki-ayanami/CVE-2025-24813★ 2githubgithub.com/pirenga/CVE-2025-24813★ 2githubgithub.com/La3B0z/CVE-2025-24813-POC★ 2githubgithub.com/MuhammadWaseem29/CVE-2025-24813★ 2githubgithub.com/gregk4sec/CVE-2025-24813★ 1githubgithub.com/f8l124/CVE-2025-24813-POC★ 1githubgithub.com/seahcy/CVE-2025-24813★ 1githubgithub.com/GadaLuBau1337/CVE-2025-24813★ 1githubgithub.com/ftz7/PoC-CVE-2025-24813★ 1githubgithub.com/tonyarris/CVE-2025-24813-PoC★ 1githubgithub.com/sentilaso1/CVE-2025-24813-Apache-Tomcat-RCE-PoC★ 1githubgithub.com/NamelessSaint8/CVE-2025-24813-POC★ 1githubgithub.com/cyglegit/CVE-2025-24813★ 1githubgithub.com/yym8538/CVE-2025-24813★ 1githubgithub.com/manjula-aw/CVE-2025-24813★ 1githubgithub.com/fatkz/CVE-2025-24813★ 1githubgithub.com/michael-david-fry/Apache-Tomcat-Vulnerability-POC-CVE-2025-24813★ 0githubgithub.com/yaleman/cve-2025-24813-poc★ 0githubgithub.com/GongWook/CVE-2025-24813★ 0githubgithub.com/horsehacks/CVE-2025-24813-checker★ 0githubgithub.com/e5dfdd568a75282b712b6d93a7a18e12/CVE-2025-24813★ 0githubgithub.com/Heimd411/CVE-2025-24813-noPoC★ 0githubgithub.com/Mega-Starmie/tomcat-cve-2025-24813-lab★ 0githubgithub.com/SebastianMautner/nuclei-CVE-2025-24813★ 0githubgithub.com/Si13NTTT/CVE-2025-24813★ 0githubgithub.com/HwangEojin/CVE-2025-24813-Tomcat11-Lab★ 0githubgithub.com/Loufa0/CVE-2025-24813★ 0githubgithub.com/gunyakit/CVE-2025-24813-PoC-exploit★ 0githubgithub.com/Dhananjayasj/CVE-2025-24813-Apache-Tomcat-Partial-PUT-Deserialization-RCE-★ 0githubgithub.com/suil12/CVE-2025-24813_presentation★ 0githubgithub.com/n0n-zer0/Spring-Boot-Tomcat-CVE-2025-24813★ 0githubgithub.com/B1gN0Se/Tomcat-CVE-2025-24813★ 0githubgithub.com/ps-interactive/lab-cve-2025-24813★ 0githubgithub.com/Affapple/CVE-2025-24813-POC★ 0githubgithub.com/JTMH37/Apache-Tomcat-CVE-2025-24813-Lab★ 0githubgithub.com/ThHardvester/CVE-2025-24813★ 0githubgithub.com/hakankarabacak/CVE-2025-24813★ 0githubgithub.com/x1ongsec/CVE-2025-24813★ 0githubgithub.com/Arthurabriel/POC-CVE-2025-24813★ 0githubgithub.com/CEAlbez/CVE-2025-24813-PoC★ 0githubgithub.com/Makavellik/POC-CVE-2025-24813-Apache-Tomcat-Remote-Code-Execution★ 0vulncheckvulncheck.com/xdb/ff7c931b911dunverifiedvulncheckvulncheck.com/xdb/1f1e1835349funverifiedvulncheckvulncheck.com/xdb/181640a7c0aeunverifiedvulncheckvulncheck.com/xdb/dbf0b83e164bunverifiedvulncheckvulncheck.com/xdb/ae2ed7271091unverifiedvulncheckvulncheck.com/xdb/165631271f8bunverifiedvulncheckvulncheck.com/xdb/6ca8e745ffa0unverifiedvulncheckvulncheck.com/xdb/bbaae546f620unverifiedvulncheckvulncheck.com/xdb/942ba42c027aunverifiedvulncheckvulncheck.com/xdb/d7e6efb852d8unverifiedvulncheckvulncheck.com/xdb/98e4bf40a0f3unverifiedcve_referencegithub.com/absholi7ly/POC-CVE-2025-24813/blob/main/README.mdunverifiedvulncheckvulncheck.com/xdb/afb2366289d2unverifiedvulncheckvulncheck.com/xdb/04473f7d3f5bunverifiedvulncheckvulncheck.com/xdb/07fe7e5e5771unverifiedvulncheckvulncheck.com/xdb/1029728ca7eaunverifiedvulncheckvulncheck.com/xdb/9c76c97103e5unverifiedvulncheckvulncheck.com/xdb/b46e0f62ba5dunverifiedvulncheckvulncheck.com/xdb/0be326ee4646unverifiedvulncheckvulncheck.com/xdb/d2328688bc63unverifiedvulncheckvulncheck.com/xdb/438c59eda6a1unverifiedvulncheckvulncheck.com/xdb/8229a5ce661eunverifiedvulncheckvulncheck.com/xdb/f95cb1d5b6afunverifiedvulncheckvulncheck.com/xdb/930571969654unverifiedvulncheckvulncheck.com/xdb/2e3eea69a36dunverifiedvulncheckvulncheck.com/xdb/2e8121be4e6cunverifiedvulncheckvulncheck.com/xdb/66bfb6dc4529unverifiedvulncheckvulncheck.com/xdb/ecda97c5692cunverifiedvulncheckvulncheck.com/xdb/62446f11b151unverifiedvulncheckvulncheck.com/xdb/9e52fea0ddb5unverifiedvulncheckvulncheck.com/xdb/5ff5b290fccdunverifiedvulncheckvulncheck.com/xdb/41039969d4bbunverifiedvulncheckvulncheck.com/xdb/e48dddb86729unverifiedvulncheckvulncheck.com/xdb/c63f2f746a4cunverifiedvulncheckvulncheck.com/xdb/40412144ed11unverifiedvulncheckvulncheck.com/xdb/a23cfd526be6unverifiedvulncheckvulncheck.com/xdb/62ff6f95bed3unverifiedvulncheckvulncheck.com/xdb/2ed807c5c32cunverifiedvulncheckvulncheck.com/xdb/31ac53ba66b2unverifiedvulncheckvulncheck.com/xdb/bec48551a957unverifiedvulncheckvulncheck.com/xdb/02795c240160unverifiedvulncheckvulncheck.com/xdb/3aff79b6f0d4unverifiedvulncheckvulncheck.com/xdb/25d3559a5ca1unverified
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.