Is CVE-2025-24813 exploited in the wild?

Yes. CVE-2025-24813 is known to be exploited in the wild, first recorded on 1 April 2025. Treat it as urgent.

How severe is CVE-2025-24813?

Critical severity, with a CVSS score of 3.1, published 10 March 2025.

Which products and versions are affected?

org.apache.tomcat:tomcat-catalina (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.3; org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.3.

How is CVE-2025-24813 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-24813?

Check whether you run Apache Tomcat, org.apache.tomcat:tomcat-catalina (Maven) or org.apache.tomcat.embed:tomcat-embed-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

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

CVE-2025-24813 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2025-03-10

Apache Tomcat contains a path equivalence vulnerability involving internal dots in filenames. When the default servlet has writes enabled and partial PUT is supported, remote attackers can achieve code execution, information disclosure, or file content injection. Remote code execution specifically requires Tomcat's file-based session persistence and a library vulnerable to deserialization.

Technologies: Apache Tomcat, org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2025-24813 exploited in the wild?: Yes. CVE-2025-24813 is known to be exploited in the wild, first recorded on 1 April 2025. Treat it as urgent.
How severe is CVE-2025-24813?: Critical severity, with a CVSS score of 3.1, published 10 March 2025.
Which products and versions are affected?: org.apache.tomcat:tomcat-catalina (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.3; org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.3.
Is there a fix for CVE-2025-24813?: Yes. org.apache.tomcat:tomcat-catalina (Maven): upgrade to 11.0.3 or later; org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 11.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-24813 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-24813?: Check whether you run Apache Tomcat, org.apache.tomcat:tomcat-catalina (Maven) or org.apache.tomcat.embed:tomcat-embed-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.tomcat:tomcat-catalina (Maven): upgrade to 11.0.3 or later

# set org.apache.tomcat:tomcat-catalina to 11.0.3 in your pom.xml or build.gradle

org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 11.0.3 or later

# set org.apache.tomcat.embed:tomcat-embed-core to 11.0.3 in your pom.xml or build.gradle

Affected products

Apache Tomcat 11.0.0-M1 through 11.0.2
Apache Tomcat 10.1.0-M1 through 10.1.34
Apache Tomcat 9.0.0.M1 through 9.0.98
Apache Tomcat 8.5.0 through 8.5.100 (EOL)

Identifiers

CVE-2025-24813
GHSA-83qj-6fr2-vhqg

Timeline

2025-03-10: disclosed: Mailing list disclosure
2025-04-01: advisory: NVD publication date
2025-04-01: kev added: Added to CISA Known Exploited Vulnerabilities Catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.