Summary
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.apache.tomcat:tomcat-catalina to 11.0.8 or later; org.apache.tomcat:tomcat-catalina to 10.1.42 or later; org.apache.tomcat:tomcat-catalina to 9.0.106 or later; org.apache.tomcat.embed:tomcat-embed-core to 11.0.8 or later; org.apache.tomcat.embed:tomcat-embed-core to 10.1.42 or later; org.apache.tomcat.embed:tomcat-embed-core to 9.0.106 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-49125? CVE-2025-49125 is a medium-severity security vulnerability in org.apache.tomcat:tomcat-catalina (maven), affecting versions >= 11.0.0-M1, <= 11.0.7. It is fixed in 11.0.8, 10.1.42, 9.0.106.
- Which packages are affected by CVE-2025-49125?
org.apache.tomcat:tomcat-catalina(maven) (versions >= 11.0.0-M1, <= 11.0.7)org.apache.tomcat.embed:tomcat-embed-core(maven) (versions >= 11.0.0-M1, <= 11.0.7)
- Is there a fix for CVE-2025-49125? Yes. CVE-2025-49125 is fixed in 11.0.8, 10.1.42, 9.0.106. Upgrade to this version or later.
- Is CVE-2025-49125 exploitable, and should I be worried? Whether CVE-2025-49125 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-49125 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-49125?
- Upgrade
org.apache.tomcat:tomcat-catalinato 11.0.8 or later - Upgrade
org.apache.tomcat:tomcat-catalinato 10.1.42 or later - Upgrade
org.apache.tomcat:tomcat-catalinato 9.0.106 or later - Upgrade
org.apache.tomcat.embed:tomcat-embed-coreto 11.0.8 or later - Upgrade
org.apache.tomcat.embed:tomcat-embed-coreto 10.1.42 or later - Upgrade
org.apache.tomcat.embed:tomcat-embed-coreto 9.0.106 or later
- Upgrade