# What is CVE-2025-24813?

> CVE-2025-24813 is a critical-severity flaw (CVSS 9.8) in Tomcat from Apache, published on 10 March 2025. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at over 99%. If you run an affected version, patch it first.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2025-24813

## At a glance

- **Verdict:** Fix this now. Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
- **Precursor Intelligence risk score:** 88 out of 100 (Critical); action: Emergency patch. Kept up to date as the evidence changes.
- **Severity:** Critical (CVSS 9.8 out of 10)
- **Known to be exploited:** Yes, it is on the government list of flaws known to be exploited
- **Chance of use in the next 30 days:** over 99% (latest exploit-likelihood forecast)
- **Published:** 10 March 2025
- **Record last updated:** 23 October 2025
- **Main product:** Tomcat from Apache
- **Affected products:** 3

## What is CVE-2025-24813? In plain terms

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### The official description

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.

### What kind of flaw is it?

- CWE-502: Deserialization of Untrusted Data
- CWE-44: Path Equivalence: 'file.name' (Internal Dot)
- CWE-706: Use of Incorrectly-Resolved Name or Reference

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read data, change data and take it offline

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

## Is CVE-2025-24813 being exploited? Yes

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at over 99%.

Exploit likelihood over the last 7 days: >99%, >99%, >99%, >99%, >99%, >99%, >99%.

### Timeline

- 10 March 2025: Published
- 23 October 2025: Record last updated

### How Precursor Intelligence ranks it

CVE-2025-24813 scores **88 out of 100 (Critical)**, with the action "Emergency patch".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2025-24813?

The published record lists 3 products. Versions are as published: "before 9.0.99" means every version up to, but not including, 9.0.99.

- [Tomcat](https://www.precursorintelligence.com/product/apache/tomcat) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): before 9.0.99, 10.1.0-milestone1, 10.1.0-milestone2, 10.1.0-milestone3, 10.1.0-milestone4, 10.1.0-milestone5, 10.1.0-milestone6, 10.1.0-milestone7, 10.1.0-milestone8, 10.1.0-milestone9, 10.1.0-milestone10, 10.1.0-milestone11, 10.1.0-milestone12, 10.1.0-milestone13, 10.1.0-milestone14, 10.1.0-milestone15, 10.1.0-milestone16, 10.1.0-milestone17, 10.1.0-milestone18, 10.1.0-milestone19, 10.1.0-milestone20, 10.1.1 to before 10.1.35, 11.0.0-milestone1, 11.0.0-milestone2, 11.0.0-milestone3, 11.0.0-milestone4, 11.0.0-milestone5, 11.0.0-milestone6, 11.0.0-milestone7, 11.0.0-milestone8, 11.0.0-milestone9, 11.0.0-milestone10, 11.0.0-milestone11, 11.0.0-milestone12, 11.0.0-milestone13, 11.0.0-milestone14, 11.0.0-milestone15, 11.0.0-milestone16, 11.0.0-milestone17, 11.0.0-milestone18 and 8 more
- [Bootstrap OS](https://www.precursorintelligence.com/product/netapp/bootstrap_os) by [Netapp](https://www.precursorintelligence.com/vendors/netapp) (Operating system): version not specified
- [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 11.0

## How do I fix CVE-2025-24813?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Check it wasn’t used before you patched.** Because criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.

### References

- [lists.apache.org](https://lists.apache.org/thread/j5fkjv2k477os90nczf2v9l61fb0kkgq) (Vendor advisory)
- [openwall.com](http://www.openwall.com/lists/oss-security/2025/03/10/5) (Mailing list, Third-party advisory)
- [lists.debian.org](https://lists.debian.org/debian-lts-announce/2025/04/msg00003.html) (Mailing list, Third-party advisory)
- [security.netapp.com](https://security.netapp.com/advisory/ntap-20250321-0001/) (Third-party advisory)
- [vicarius.io](https://www.vicarius.io/vsociety/posts/cve-2025-24813-detect-apache-tomcat-rce) (Issue tracking)
- [vicarius.io](https://www.vicarius.io/vsociety/posts/cve-2025-24813-mitigate-apache-tomcat-rce) (Issue tracking)
- [vicarius.io](https://www.vicarius.io/vsociety/posts/cve-2025-24813-tomcat-detect-vulnerability) (Issue tracking)
- [vicarius.io](https://www.vicarius.io/vsociety/posts/cve-2025-24813-tomcat-mitigation-vulnerability) (Issue tracking)
- [github.com](https://github.com/absholi7ly/POC-CVE-2025-24813/blob/main/README.md) (Exploit)
- [cisa.gov](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24813) (Third-party advisory, Government resource)

## Questions

### What is CVE-2025-24813?

CVE-2025-24813 is a critical-severity flaw in Tomcat from Apache, published on 10 March 2025. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2025-24813?

It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2025-24813 is 88 out of 100, which is Critical. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.

### Is CVE-2025-24813 being exploited?

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at over 99%.

### Which versions does CVE-2025-24813 affect?

For Tomcat from Apache: before 9.0.99, 10.1.0-milestone1, 10.1.0-milestone2, 10.1.0-milestone3, 10.1.0-milestone4, 10.1.0-milestone5 and 42 more. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2025-24813?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.

## Does CVE-2025-24813 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact