Skip to content

CVE-2025-24813

Is CVE-2025-24813 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Yes
CISA KEV · Apr 1, 2025
Public exploit
Metasploit +2
Metasploit/EDB/PoC
Base severity
9.8 Critical
CVSS
Exploitation prob.
100%
FIRST EPSS
Weakness
CWE-44
CWE

Confirmed exploited in the wild. Patch this first, regardless of the base score.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
Active
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Attend
  • high impact → Act

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

public exploits

links to sources — we don’t host code

A working exploit is publicly available from a maintained source. Treat this as higher urgency and verify your exposure.

affected packages

GHSA-83qj-6fr2-vhqg · GitHub rates it critical
  • Mavenorg.apache.tomcat:tomcat-catalina
    Vulnerable
    ≥ 11.0.0-M1, < 11.0.3; ≥ 10.1.0-M1, < 10.1.35; ≥ 9.0.0.M1, < 9.0.99; ≥ 8.5.0, ≤ 8.5.100
    Fixed in
    11.0.3, 10.1.35, 9.0.99
  • Mavenorg.apache.tomcat.embed:tomcat-embed-core
    Vulnerable
    ≥ 11.0.0-M1, < 11.0.3; ≥ 10.1.0-M1, < 10.1.35; ≥ 9.0.0.M1, < 9.0.99; ≥ 8.5.0, ≤ 8.5.100
    Fixed in
    11.0.3, 10.1.35, 9.0.99

Source: GitHub Advisory Database (CC-BY 4.0), via OSV.dev. Check your lockfile version against the ranges above.

baseline read

auto · not a community verdict

Real — exploited in the wild

CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.

Based on CISA KEV

Confirm or dispute →

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

Published · Added to CISA KEV (22 days after publication)

Embed this verdict
TruePositive verdict for CVE-2025-24813
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2025-24813/badge.svg)](https://www.truepositive.app/cve/CVE-2025-24813)
HTML
<a href="https://www.truepositive.app/cve/CVE-2025-24813"><img src="https://www.truepositive.app/cve/CVE-2025-24813/badge.svg" alt="TruePositive verdict for CVE-2025-24813"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. CISA SSVC assessment · exploitation: active
  2. Added to CISA KEV · confirmed exploited in the wild
  3. Added to VulnCheck KEV · reported exploited in the wild
  4. Published by NVD

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    Apache Tomcat Path Equivalence Vulnerability — 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. Listed in the CISA KEV catalog (added 2025-04-01) — confirmed exploited in the wild, not theoretical. FIRST EPSS puts the chance of exploitation in the next 30 days at ~100%. Treat it as real and prioritize remediation over triage.

  • 0
    Remediation · TruePositive EditorialCurated

    Required action for Apache Tomcat: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. CISA set a federal remediation due date of 2025-04-22. After patching, verify the vulnerable path is no longer reachable before closing the finding.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.