dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Apr 2025.
TomcatWeb server / proxy · Apache

CVE-2025-24813

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 9.0.99 / 10.1.35 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tomcat contains a path equivalence vulnerability ('file.Name' - Internal Dot) in the Default Servlet. When writes are enabled (disabled by default) and partial PUT support is enabled (enabled by default), attackers can perform partial file overwrites to inject malicious content into uploaded files, expose sensitive files, or achieve RCE via deserialization if Tomcat's file-based session persistence is used with a vulnerable library.

MitigationUpgrade to Apache Tomcat 11.0.3, 10.1.35, or 9.0.99. Additionally, ensure the default servlet's write functionality remains disabled unless explicitly required, and consider disabling partial PUT if not needed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:< 9.0.99>= 10.1.1, < 10.1.35>= 11.0.1, < 11.0.3= 10.1.0= 11.0.0
Debian LinuxOperating system
Affected:= 11.0
Bootstrap OsOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Tomcat version
    Locate the Tomcat installation and check the version. Common locations: the serverinfo.properties file in the lib folder, the release notes, or the filename of the catalina.jar. Alternatively, check the SERVER_INFO variable returned by the servlet or the version reported by the startup scripts.
    Affected if Version is 9.0.x below 9.0.99, 10.1.0 through 10.1.34 inclusive, or 11.0.0 through 11.0.2 inclusive
  2. Confirm write is enabled in the Default Servlet
    Inspect the Default Servlet configuration in the application's web.xml or the global conf/web.xml. Look for a <servlet> element with <servlet-name>default</servlet-name> and check the <init-param> for <param-name>readonly</param-name>. If the value is set to false, or if the parameter is absent (defaults to false), writes are enabled.
    Affected if The Default Servlet readonly init parameter is set to false or is not explicitly set to true
  3. Confirm partial PUT support is enabled
    Review the servlet configuration to determine if partial PUT requests are accepted. This is typically not a default feature in the standard Default Servlet, but check for any custom servlets or filters that handle PUT requests with partial content capabilities, or any configuration that enables this in the servlet container.
    Affected if Partial PUT functionality is enabled and accessible to unauthenticated attackers
  4. Check for file-based session persistence
    Examine the application's context.xml or the global server.xml for a <Manager> element. If a pathname attribute is present (for example, pathname="SESSIONS.ser"), Tomcat is configured to persist sessions to disk. Also check the classpath for vulnerable deserialization libraries in the lib folder.
    Affected if File-based session persistence is configured and vulnerable deserialization libraries exist in the classpath (required for RCE)

The environment is affected if the Tomcat version is in the vulnerable range AND write is enabled on the Default Servlet AND partial PUT is accessible; RCE specifically also requires file-based session persistence with a vulnerable library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.99 / 10.1.35 / 11.0.3 or later
Fixed in 9.0.9910.1.3511.0.3
Interim mitigation

Upgrade to Apache Tomcat 11.0.3, 10.1.35, or 9.0.99. Additionally, ensure the default servlet's write functionality remains disabled unless explicitly required, and consider disabling partial PUT if not needed.

Recommended fix High confidence

Apache Tomcat 9.0.99 / 10.1.35 / 11.0.3 (depending on major version in use)

  1. 1. Identify the currently running Apache Tomcat version by checking the $CATALINA_HOME/lib/catalina.jar manifest or running 'version.sh'
  2. 2. For Tomcat 11.x users: Upgrade to version 11.0.3 or later
  3. 3. For Tomcat 10.1.x users: Upgrade to version 10.1.35 or later
  4. 4. For Tomcat 9.x users: Upgrade to version 9.0.99 or later
  5. 5. Download the appropriate Tomcat version from https://tomcat.apache.org/download-90.cgi (for 9.x), https://tomcat.apache.org/download-10.cgi (for 10.1.x), or https://tomcat.apache.org/download-11.cgi (for 11.x)
  6. 6. Stop the Tomcat service gracefully
  7. 7. Backup the existing Tomcat installation directory including conf/ and webapps/
  8. 8. Replace the Tomcat installation with the new version, preserving your configuration files
Caveat Minimal risk - point releases within same major version typically maintain backward compatibility; however, always test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24813 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data