NewsCompaniesFlawsGuides
Get the app

CVE-2025-24813

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Apache Tomcat. For every flaw being used in attacks, see Exploited flaws; for Apache’s, see Apache flaws being used in attacks.

CVE-2025-24813 is a security flaw in Apache Tomcat, a server for running Java web applications. Attackers can run their own code on Apache Tomcat. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 1 Apr 2025.[1]

Apache Tomcat is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Apache has published a fix or advice.

Description

CISA calls it a path equivalence in Apache Tomcat. In its words: “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.”[1]

The CVE record adds: “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…”[2]

The underlying weakness is CWE-44, deserialization of untrusted data (CWE-502), in MITRE’s list of common software weaknesses.

It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Apache’s advisory has them[3]. CISA names the product as Apache Tomcat.

Most families won’t have Apache Tomcat; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 1 Apr 2025, 22 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 22 Apr 2025 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Apache has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Apache Tomcat is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 22 Apr 2025 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4]

See also

Other Apache Tomcat flaws

Other Apache flaws

  • CVE-2016-3081, Apache Struts: command injection ·
  • CVE-2026-34197, Apache ActiveMQ: improper input validation ·
  • CVE-2024-38475, Apache HTTP Server: improper escaping of output ·
  • CVE-2024-45195, Apache OFBiz: forced browsing ·
  • CVE-2024-27348, Apache HugeGraph-Server: improper access control ·

Every Apache flaw on CISA’s list · Everything added in April 2025

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Apache Tomcat Path Equivalence Vulnerability”. Known Exploited Vulnerabilities Catalog, added 1 Apr 2025.
  2. ^ National Institute of Standards and Technology. “CVE-2025-24813 Detail”. National Vulnerability Database, published 10 Mar 2025.
  3. ^ Apache. Advisories and fixes: lists.apache.org.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.999, percentile 100.0, 31 Oct 2026.
  5. CVE Program. “CVE-2025-24813”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.