CVE-2025-49125 is a high-severity (CVSS 7.5) CWE-288 vulnerability in org.apache.tomcat:tomcat-catalina. A fix is available for org.apache.tomcat:tomcat-catalina — see the affected versions and patch details below.
Apache Tomcat: Security constraint bypass for pre/post-resources
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-49125.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat.embed:tomcat-embed-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Authentication Bypass Using an Alternate Path or Channel vulnerability in Apache Tomcat. When using PreResources or PostResources mounted other than at the root of the web application, it was possible to access those resources via an unexpected path. That path was likely not to be protected by the same security constraints as the expected path, allowing those security constraints to be bypassed.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0-M1 through 10.1.41, from 9.0.0.M1 through 9.0.105. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 through 8.5.100. Other, older, EOL versions may also be affected.
Users are recommended to upgrade to version 11.0.8, 10.1.42 or 9.0.106, which fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-catalina | ≥ 11.0.0-M1&&< 11.0.8 | 11.0.8org.apache.tomcat:tomcat-catalina:11.0.8 |
| ☕Maven | org.apache.tomcat:tomcat-catalina | ≥ 10.1.0-M1&&< 10.1.42 | 10.1.42org.apache.tomcat:tomcat-catalina:10.1.42 |
| ☕Maven | org.apache.tomcat:tomcat-catalina | ≥ 9.0.0.M1&&< 9.0.106 | 9.0.106org.apache.tomcat:tomcat-catalina:9.0.106 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 11.0.0-M1&&< 11.0.8 | 11.0.8org.apache.tomcat.embed:tomcat-embed-core:11.0.8 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 10.1.0-M1&&< 10.1.42 | 10.1.42org.apache.tomcat.embed:tomcat-embed-core:10.1.42 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 9.0.0.M1&&< 9.0.106 | 9.0.106org.apache.tomcat.embed:tomcat-embed-core:9.0.106 |
Affected Products
tomcatapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-catalina, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat-catalina to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49125 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2025-49125 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | tomcat9-1:9.0.87-5.el10_0.3 | RHSA-2025:14178 |
| Red Hat Enterprise Linux 10 | tomcat-1:10.1.36-1.el10_0.2 | RHSA-2025:14179 |
| Red Hat Enterprise Linux 8 | tomcat-1:9.0.87-1.el8_10.6 | RHSA-2025:14177 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | tomcat-1:9.0.87-1.el8_8.7 | RHSA-2025:14182 |
| Red Hat Enterprise Linux 9 | tomcat-1:9.0.87-3.el9_6.3 | RHSA-2025:14181 |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | tomcat-1:9.0.87-1.el9_2.6 | RHSA-2025:14183 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | tomcat-1:9.0.87-1.el9_4.6 | RHSA-2025:14180 |
| Red Hat JBoss Web Server 5.8.5 | tomcat-catalina | RHSA-2025:11696 |
Frequently Asked Questions
Is CVE-2025-49125 in your dependencies?
Find it across Maven, including transitive dependencies.