basicsecurity.net
Proof, not just disclosure.
Threats / Apache / CVE-2025-24813
CVE-2025-24813 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Apache Tomcat vulnerability

Apache Tomcat path equivalence vulnerability allows remote code execution, information disclosure, or content injection through partial PUT requests.

Verdict

Today item — known-exploited.

A path equivalence flaw in Apache Tomcat enables unauthenticated remote attackers to execute arbitrary code, access sensitive information, or inject malicious content via crafted partial PUT requests. Active exploitation observed in the wild.

CISA KEV Yes · 2025-04-013EPSS 0.99945 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
102 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-04-01).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99945 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apache, Tomcat. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-44 CWE-44, CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a partial PUT request that exploits path equivalence to bypass access controls and reach restricted resources.
Business
Attackers gain unauthorized access to application files and system resources without authentication.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I inject malicious code or content into the application through the path equivalence vulnerability.
Business
Compromised application integrity leads to malware distribution, data tampering, and loss of customer trust.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code on the Tomcat server by leveraging the vulnerability in request handling.
Business
Full server compromise enables data exfiltration, lateral movement, and operational disruption.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 102 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by apache (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by apacheCNA
    Credited with finding itCOSCO Shipping Lines DICfindersw0rd1ight (https://github.com/sw0rd1ight)finder