Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-24813: Apache Tomcat Path Equivalence Vulnerability

99
Patch now
CRITICAL 9.8EXPLOITEDREMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2025-24813 is a critical-severity flaw (CVSS 9.8) affecting tomcat, debian linux, bootstrap os, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.1

Why this priority

  • Critical severity
  • EPSS top 1%: very likely to be exploited
  • Exploited in the wild (CISA KEV)
  • Public exploit reference
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance99.9% (top 1%)
CISA exploited listYes, fix due 2025-04-22
WeaknessCWE-44, CWE-502, CWE-706
Published2025-03-10
Last modified2026-06-17
Publisher (CNA): Apache Software Foundation · Vendor: apache · debian · netapp

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache tomcat UPGRADE
Affected: < 9.0.99 · >= 10.1.1 and < 10.1.35 · >= 11.0.1 and < 11.0.3 · 10.1.0 milestone1 · 10.1.0 milestone10 · 10.1.0 milestone11 · 10.1.0 milestone12 · 10.1.0 milestone13
Fixed in: 9.0.99, 10.1.35, 11.0.3
Safe to downgrade to: a release before 10.1.0
1. Check installed version
apt-cache policy tomcat || rpm -q tomcat || tomcat --version
2. UPGRADE to 9.0.99 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade tomcat
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade tomcat
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 10.1.0 (Debian / Ubuntu)
apt-cache madison tomcat sudo apt install tomcat=<VERSION_BEFORE_10.1.0> sudo apt-mark hold tomcat
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list tomcat sudo dnf downgrade tomcat-<VERSION_BEFORE_10.1.0> sudo dnf versionlock add tomcat
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
debian debian linux MITIGATE
Affected: 11.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 11.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
netapp bootstrap os MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
Maven · org.apache.tomcat:tomcat-catalina · FIXED · 11.0.3 · vulnerable: >= 11.0.0-M1, < 11.0.3 · source
Set org.apache.tomcat:tomcat-catalina to 11.0.3 or later in pom.xml or build.gradle, then rebuild and redeploy.
Maven · org.apache.tomcat.embed:tomcat-embed-core · FIXED · 11.0.3 · vulnerable: >= 11.0.0-M1, < 11.0.3 · source
Set org.apache.tomcat.embed:tomcat-embed-core to 11.0.3 or later in pom.xml or build.gradle, then rebuild and redeploy.
Fedora 46 · perl-WWW-OrangeHRM-Client · FIXED · 0.12.0-21.fc46 · FEDORA-2026-2d14efca09 · source
sudo dnf upgrade --advisory=FEDORA-2026-2d14efca09
Ubuntu 24.04 · tomcat9 · FIXED · 9.0.70-2ubuntu0.1+esm1
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.70-2ubuntu0.1+esm1" && echo PATCHED || echo STILL-VULNERABLE
Ubuntu 20.04 · tomcat9 · FIXED · 9.0.31-1ubuntu0.9+esm1
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.31-1ubuntu0.9+esm1" && echo PATCHED || echo STILL-VULNERABLE
Ubuntu 22.04 · tomcat9 · FIXED · 9.0.58-1ubuntu0.2+esm2
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.58-1ubuntu0.2+esm2" && echo PATCHED || echo STILL-VULNERABLE
Ubuntu 24.10 · tomcat9 · FIXED · 9.0.70-2ubuntu1.24.10.1
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.70-2ubuntu1.24.10.1" && echo PATCHED || echo STILL-VULNERABLE
Ubuntu 25.04 · tomcat9 · FIXED · 9.0.70-2ubuntu1.25.04.1
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.70-2ubuntu1.25.04.1" && echo PATCHED || echo STILL-VULNERABLE
Debian 12 · tomcat10 · FIXED · 10.1.34-0+deb12u2
sudo apt update && sudo apt install --only-upgrade tomcat10 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat10)" ge "10.1.34-0+deb12u2" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · tomcat10 · FIXED · 10.1.35-1
sudo apt update && sudo apt install --only-upgrade tomcat10 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat10)" ge "10.1.35-1" && echo PATCHED || echo STILL-VULNERABLE
Debian 12 · tomcat9 · FIXED · 9.0.70-2
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.70-2" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · tomcat9 · FIXED · 9.0.70-2
sudo apt update && sudo apt install --only-upgrade tomcat9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' tomcat9)" ge "9.0.70-2" && echo PATCHED || echo STILL-VULNERABLE
RHEL 10 · tomcat9 · FIXED · tomcat9-9.0.87-5.el10_0
sudo dnf upgrade --advisory=RHSA-2025:7494 rpm -q tomcat9
RHEL 10 · tomcat · FIXED · tomcat-10.1.36-1.el10_0
sudo dnf upgrade --advisory=RHSA-2025:7497 rpm -q tomcat
RHEL 8 · tomcat · FIXED · tomcat-9.0.87-1.el8_10.3
sudo dnf upgrade --advisory=RHSA-2025:3683 rpm -q tomcat
RHEL 8.8 Extended Update Support · tomcat · FIXED · tomcat-9.0.87-1.el8_8.4
sudo dnf upgrade --advisory=RHSA-2025:3684 rpm -q tomcat
RHEL 9 · tomcat · FIXED · tomcat-9.0.87-2.el9_5.1
sudo dnf upgrade --advisory=RHSA-2025:3645 rpm -q tomcat
Amazon Linux 2023 · see advisory · FIXED · ALAS2023-2025-911 · source
sudo dnf update --advisory=ALAS2023-2025-911
Amazon Linux 2 · see advisory · FIXED · ALAS2-2025-2812 · source
sudo yum update --advisory=ALAS2-2025-2812
Amazon Linux 1 · see advisory · FIXED · ALAS-2025-1969 · source
sudo yum update --advisory=ALAS-2025-1969

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Advisories and coverage

Research and news

Verify at the official source NVD · CVE Program · CISA KEV catalog · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-24813?

tomcat: upgrade to 9.0.99, 10.1.35, 11.0.3; debian linux: mitigate or apply the listed mitigation; bootstrap os: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-24813 being exploited?

Yes. CVE-2025-24813 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

What does CVE-2025-24813 affect?

CVE-2025-24813 affects tomcat, debian linux, bootstrap os. Severity is critical (CVSS 9.8). 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 Tomc

How urgent is CVE-2025-24813?

Priority 99/100. Critical severity; EPSS top 1%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Apache Tomcat vulnerabilities · Debian vulnerabilities · Bootstrap vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.