CVE-2025-24813

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-04-01), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 2,402 internet-exposed hosts are running an affected version right now
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 9.8Exploit: NoneExposed: 2,402

A fix is available — apply it.

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.

Live · internet exposure

2,402 internet-exposed hosts are running an affected version of CVE-2025-24813 right now.

across 94 countries (China, United States, Korea, Republic of, Germany, India)top: tomcat
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
100.0%
KEV
⚠ Exploited

Published

March 10, 2025

Last Modified

October 23, 2025

Advisory Details (10)

Auto-updated May 31, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24813
generic🟡 PoC Available

POC-CVE-2025-24813/README.md at main · absholi7ly/POC-CVE-2025-24813 · GitHub

https://github.com/absholi7ly/POC-CVE-2025-24813/blob/main/README.md
generic

CVE-2025-24813: Tomcat Detect Vulnerability - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-24813-tomcat-detect-vulnerability
generic

CVE-2025-24813: Mitigate Apache Tomcat RCE - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-24813-mitigate-apache-tomcat-rce
generic

CVE-2025-24813: Detect Apache Tomcat RCE - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-24813-detect-apache-tomcat-rce
generic Patch Available

[SECURITY] [DLA 4108-1] tomcat9 security update

https://lists.debian.org/debian-lts-announce/2025/04/msg00003.html
generic

oss-security - CVE-2025-24813: Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUT

http://www.openwall.com/lists/oss-security/2025/03/10/5

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat9-user (9.0.58-1ubuntu0.2+esm2) @ jammy2026-07-13ubuntu
ubuntulibtomcat9-java (9.0.70-2ubuntu1.24.10.1) @ oracular2026-07-13ubuntu
redhattomcat-1:10.1.36-1.el10_02025-05-13redhat
redhattomcat9-1:9.0.87-5.el10_02025-05-13redhat
redhattomcat-1:9.0.87-1.el8_10.32025-04-08redhat
redhattomcat-1:9.0.87-1.el8_8.42025-04-08redhat
redhattomcat-1:9.0.87-2.el9_5.12025-04-07redhat
redhatjws6-tomcat-0:10.1.36-6.redhat_00007.1.el9jws2025-04-07redhat
redhattomcat-1:9.0.87-1.el9_4.32025-04-07redhat
redhattomcat2025-04-07redhat
redhattomcat-1:9.0.87-1.el9_2.32025-04-07redhat
redhatjws5-tomcat-0:9.0.87-8.redhat_00008.1.el9jws2025-04-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat.embed:tomcat-embed-core8.5.0 ... 8.5.99 (85 versions)
org.apache.tomcat:tomcat-catalina8.5.0 ... 8.5.99 (85 versions)

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 93× in last 7d / 393× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 577 total refreshes for this CVE.

  1. 2026-07-13 22:26 UTCEG score recompute
  2. 2026-07-13 22:26 UTCVendor advisory
  3. 2026-07-13 18:39 UTCEG score recompute
  4. 2026-07-13 18:39 UTCVendor advisory
  5. 2026-07-13 17:07 UTCCISA KEV update
  6. 2026-07-13 14:52 UTCEG score recompute
  7. 2026-07-13 14:52 UTCVendor advisory
  8. 2026-07-13 11:05 UTCEG score recompute
  9. 2026-07-13 11:05 UTCVendor advisory
  10. 2026-07-13 07:18 UTCEG score recompute
  11. 2026-07-13 07:18 UTCVendor advisory
  12. 2026-07-13 03:31 UTCEG score recompute
  13. 2026-07-13 03:31 UTCVendor advisory
  14. 2026-07-12 23:44 UTCEG score recompute
  15. 2026-07-12 23:44 UTCVendor advisory
  16. 2026-07-12 19:57 UTCEG score recompute
  17. 2026-07-12 19:57 UTCVendor advisory
  18. 2026-07-12 16:10 UTCEG score recompute
  19. 2026-07-12 16:10 UTCVendor advisory
  20. 2026-07-12 12:22 UTCEG score recompute
  21. 2026-07-12 12:22 UTCVendor advisory
  22. 2026-07-12 08:35 UTCEG score recompute
  23. 2026-07-12 08:35 UTCVendor advisory
  24. 2026-07-12 04:48 UTCEG score recompute
  25. 2026-07-12 04:48 UTCVendor advisory
Show 75 more
  1. 2026-07-12 01:01 UTCEG score recompute
  2. 2026-07-12 01:01 UTCVendor advisory
  3. 2026-07-11 21:14 UTCEG score recompute
  4. 2026-07-11 21:14 UTCVendor advisory
  5. 2026-07-11 17:27 UTCEG score recompute
  6. 2026-07-11 17:27 UTCVendor advisory
  7. 2026-07-11 13:40 UTCEG score recompute
  8. 2026-07-11 13:40 UTCVendor advisory
  9. 2026-07-11 09:52 UTCEG score recompute
  10. 2026-07-11 09:52 UTCVendor advisory
  11. 2026-07-11 06:06 UTCEG score recompute
  12. 2026-07-11 06:06 UTCVendor advisory
  13. 2026-07-11 02:17 UTCEG score recompute
  14. 2026-07-11 02:17 UTCVendor advisory
  15. 2026-07-10 22:29 UTCEG score recompute
  16. 2026-07-10 22:29 UTCVendor advisory
  17. 2026-07-10 18:42 UTCEG score recompute
  18. 2026-07-10 18:42 UTCVendor advisory
  19. 2026-07-10 17:52 UTCCISA KEV update
  20. 2026-07-10 14:55 UTCEG score recompute
  21. 2026-07-10 14:55 UTCVendor advisory
  22. 2026-07-10 11:08 UTCEG score recompute
  23. 2026-07-10 11:08 UTCVendor advisory
  24. 2026-07-10 07:21 UTCEG score recompute
  25. 2026-07-10 07:21 UTCVendor advisory
  26. 2026-07-10 03:33 UTCEG score recompute
  27. 2026-07-10 03:33 UTCVendor advisory
  28. 2026-07-09 23:44 UTCEG score recompute
  29. 2026-07-09 23:44 UTCVendor advisory
  30. 2026-07-09 19:57 UTCEG score recompute
  31. 2026-07-09 19:57 UTCVendor advisory
  32. 2026-07-09 19:09 UTCEPSS rescore
  33. 2026-07-09 16:10 UTCEG score recompute
  34. 2026-07-09 16:10 UTCVendor advisory
  35. 2026-07-09 12:23 UTCEG score recompute
  36. 2026-07-09 12:23 UTCVendor advisory
  37. 2026-07-09 08:36 UTCEG score recompute
  38. 2026-07-09 08:36 UTCVendor advisory
  39. 2026-07-09 04:48 UTCEG score recompute
  40. 2026-07-09 04:48 UTCVendor advisory
  41. 2026-07-09 01:01 UTCEG score recompute
  42. 2026-07-09 01:01 UTCVendor advisory
  43. 2026-07-08 21:14 UTCEG score recompute
  44. 2026-07-08 21:14 UTCVendor advisory
  45. 2026-07-08 17:25 UTCEG score recompute
  46. 2026-07-08 17:25 UTCVendor advisory
  47. 2026-07-08 13:38 UTCEG score recompute
  48. 2026-07-08 13:38 UTCVendor advisory
  49. 2026-07-08 09:49 UTCEG score recompute
  50. 2026-07-08 09:49 UTCVendor advisory
  51. 2026-07-08 06:02 UTCEG score recompute
  52. 2026-07-08 06:02 UTCVendor advisory
  53. 2026-07-08 02:15 UTCEG score recompute
  54. 2026-07-08 02:15 UTCVendor advisory
  55. 2026-07-07 22:27 UTCEG score recompute
  56. 2026-07-07 22:27 UTCVendor advisory
  57. 2026-07-07 19:01 UTCCISA KEV update
  58. 2026-07-07 18:41 UTCEG score recompute
  59. 2026-07-07 18:41 UTCVendor advisory
  60. 2026-07-07 17:16 UTCCISA KEV update
  61. 2026-07-07 14:53 UTCEG score recompute
  62. 2026-07-07 14:53 UTCVendor advisory
  63. 2026-07-07 11:05 UTCEG score recompute
  64. 2026-07-07 11:05 UTCVendor advisory
  65. 2026-07-07 07:17 UTCEG score recompute
  66. 2026-07-07 07:17 UTCVendor advisory
  67. 2026-07-07 03:30 UTCEG score recompute
  68. 2026-07-07 03:30 UTCVendor advisory
  69. 2026-07-06 23:43 UTCEG score recompute
  70. 2026-07-06 23:43 UTCVendor advisory
  71. 2026-07-06 19:56 UTCEG score recompute
  72. 2026-07-06 19:56 UTCVendor advisory
  73. 2026-07-06 16:08 UTCEG score recompute
  74. 2026-07-06 16:08 UTCVendor advisory
  75. 2026-07-06 12:21 UTCEG score recompute

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdrcrypterdotru/Apache-GOExploiter
    First seen Aug 31, 2025

    Apache (CVE-2025-24813) GOExploiter Checker & Exploiter very Fast

    Open source ↗
  • GitHub PoCx00byte/PutScanner
    First seen Jul 19, 2025

    A tool that identifies writable web directories in Apache Tomcat via HTTP PUT method [CVE-2025-24813]

    Open source ↗
  • GitHub PoCmbanyamer/Apache-Tomcat---Remote-Code-Execution-via-Session-Deserialization-CVE-2025-24813-
    First seen May 25, 2025

    Apache Tomcat - Remote Code Execution via Session Deserialization (CVE-2025-24813)

    Open source ↗
  • GitHub PoCFranconyu/Poc_for_CVE-2025-24813
    First seen Apr 10, 2025

    CVE-2025-24813 poc

    Open source ↗
  • Exploit-DBEDB-52134
    First seen Apr 7, 2025

    Apache Tomcat 11.0.3 - Remote Code Execution

    Open source ↗
  • GitHub PoCu238/Tomcat-CVE_2025_24813
    First seen Mar 24, 2025

    A playground to test the RCE exploit for tomcat CVE-2025-24813

    Open source ↗
  • GitHub PoCmsadeghkarimi/CVE-2025-24813-Exploit
    First seen Mar 18, 2025

    Apache Tomcat Remote Code Execution (RCE) Exploit - CVE-2025-24813

    Open source ↗
  • GitHub PoCcharis3306/CVE-2025-24813
    First seen Mar 16, 2025

    CVE-2025-24813利用工具

    Open source ↗
  • GitHub PoCabsholi7ly/POC-CVE-2025-24813
    First seen Mar 14, 2025

    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.

    Open source ↗
  • GitHub PoCqzy0x/cve-2025-24813_poc
    First seen Mar 14, 2025

    cve-2025-24813验证脚本

    Open source ↗

Frequently asked(6)

What is CVE-2025-24813?
CVE-2025-24813 is a critical vulnerability published on March 10, 2025. 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…
When was CVE-2025-24813 disclosed?
CVE-2025-24813 was first published in the National Vulnerability Database on March 10, 2025, with the most recent update on October 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24813 actively exploited?
Yes. CISA added CVE-2025-24813 to the Known Exploited Vulnerabilities catalog on April 1, 2025, affecting Apache Tomcat. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-24813?
CVE-2025-24813 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2025-24813?
CVE-2025-24813 affects Apache Tomcat. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-24813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24813, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-24813

Explore →

Is Your Infrastructure Affected by CVE-2025-24813?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.