← Back to KEV catalog

CVE-2025-24813

Exploitation: active CVSS 10.0 CRITICAL

CVSS base score: 10.0 (Critical) CISA · v3.1

Score assigned by CISA's Vulnrichment program; the vendor's CVE record did not include one. Vulnrichment source record →

Apache Tomcat Path Equivalence Vulnerability

Vendor: Apache   Product: Tomcat

Description

Apache Tomcat contains a path equivalence vulnerability that allows a remote attacker to execute code, disclose information, or inject malicious content via a partial PUT request. This vulnerability can be chained with CVE‑2026‑34486.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Referenced in Advisories

DateAdvisoryIssuer
2025-04-03 2025-014: Critical Vulnerability in Apache Tomcat CERT-EU

Lifecycle Timeline

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 138 points from 2025-03-15, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 99.9% on 2026-06-20.

Published Applicability

Red Hat CSAF/VEX 11 affected · 122 fixed · 27 not affected
OSV.dev (incl. GHSA) 15 affected · 12 fixed · 0 not affected
CVE List v5 (CNA container) 4 affected · 0 fixed · 0 not affected

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Detection & Exploitation

Host / SIEM
none published

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and filtered to repositories that are still online, contain code, and are starred or at least two weeks old. They are still not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm an exploit was referenced but carry no date. This product uses data from the NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

First seenToolEvidenceEarliest reference
2025-03-13 GitHub PoC Unvetted — public repository iSee857/CVE-2025-24813-PoC +49 more
2025-03-19 Metasploit Direct — curated exploit code Tomcat Partial PUT Java Deserialization
2025-04-07 Exploit-DB Direct — curated exploit code Apache Tomcat 11.0.3 - Remote Code Execution

Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.

Distribution Status

Debian · tomcat10 bookworm 10.1.34-0+deb12u2 trixie 10.1.35-1 forky 10.1.35-1 sid 10.1.35-1 scope: local
Debian · tomcat9 bookworm 9.0.70-2 trixie 9.0.70-2 forky 9.0.70-2 sid 9.0.70-2 scope: local

Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.

Fix & Cross-References

Patch and commit links and ecosystem advisory ids as published by OSV.dev. Links are listed as published, not vetted.

CISA Assessment (Vulnrichment / SSVC)

active
no
total
10.0 CRITICAL
—
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE-44 — Path Equivalence: 'file.name' (Internal Dot)
2025-03-10

Federal Remediation Window (BOD 26-04)

Yes — added 2025-04-01
no
total control
If the asset isRemediate withinTable 1 row
Publicly exposed 3 days + forensic triage 3 of 16
Not publicly exposed 14 days 11 of 16

BOD 26-04 replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.

External References