What is CVE-2025-24813?A critical-severity flaw criminals are using now.
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.
Published 10 March 2025. Record last updated 23 October 2025. We keep this page's data up to date.
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.
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-44Path Equivalence: 'file.name' (Internal Dot)
- CWE-502Deserialization of Untrusted Data
- CWE-706Use of Incorrectly-Resolved Name or Reference
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan 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%.
Timeline
- Published
- Record last updated
CVE-2025-24813 scores 88. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2025-24813 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2025-24813? 3 products.
The published record lists 3 products from 3 vendors. Versions are shown as published: "before 9.0.99" means every version up to, but not including, 9.0.99. If you run one of these, check your version, then go to the fix below.
- Application
Tomcat
by Apache
Affected versionsbefore 9.0.9910.1.0-milestone110.1.0-milestone210.1.0-milestone310.1.0-milestone410.1.0-milestone510.1.0-milestone610.1.0-milestone710.1.0-milestone810.1.0-milestone910.1.0-milestone1010.1.0-milestone1110.1.0-milestone1210.1.0-milestone13 - Operating system
Bootstrap OS
by Netapp
Affected versionsversion not specified - Operating system
Debian Linux
by Debian
Affected versions11.0
How do I fix CVE-2025-24813? Four steps.
- Check whether you run itCompare 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.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
References
10 links- J5fkjv2k477os90nczf2v9l61fb0kkgq (opens in a new tab)apache.org
- oss-security mailing list post, 10 Mar 2025 (opens in a new tab)openwall.com · 2025
- Msg00003 (opens in a new tab)debian.org · 2025
- Ntap 20250321 0001 (opens in a new tab)netapp.com
- Advisory for CVE-2025-24813 (opens in a new tab)vicarius.io
- Advisory for CVE-2025-24813 (opens in a new tab)vicarius.io
Does CVE-2025-24813 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Path Equivalence: 'file.Name' (Internal Dot) leading to Remote Code Execution and/or Information disclosure and/or malicious content added to uploaded files ...
- Matched to
- Tomcat on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
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.
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.
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%.
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.
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.