CVE-2025-49124 is a high-severity (CVSS 8.4) CWE-426 vulnerability in org.apache.tomcat.embed:tomcat-embed-core. A fix is available for org.apache.tomcat.embed:tomcat-embed-core — see the affected versions and patch details below.
Apache Tomcat: exe side-loading via icalcs.exe in Tomcat installer for Windows
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-49124.
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.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina+1 moreReal-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
Untrusted Search Path vulnerability in Apache Tomcat installer for Windows. During installation, the Tomcat installer for Windows used icacls.exe without specifying a full path.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0 through 10.1.41, from 9.0.23 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 and 7.0.95 through 7.0.109. Other 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.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&&< 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.23&&< 9.0.106 | 9.0.106org.apache.tomcat.embed:tomcat-embed-core:9.0.106 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 11.0.0-M1&&< 11.0.8 | 11.0.8org.apache.tomcat:tomcat:11.0.8 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 10.1.0&&< 10.1.42 | 10.1.42org.apache.tomcat:tomcat:10.1.42 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 9.0.23&&< 9.0.106 | 9.0.106org.apache.tomcat:tomcat: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.embed:tomcat-embed-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat.embed:tomcat-embed-core to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49124 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-49124 in your dependencies?
Find it across Maven, including transitive dependencies.