GHSA-2rvv-w9r2-rg7m is a medium-severity (CVSS 5.9) Information Exposure vulnerability in org.apache.tomcat.embed:tomcat-embed-core. EPSS puts its 30-day exploitation probability at 22.9% (98th percentile). A fix is available for org.apache.tomcat.embed:tomcat-embed-core — see the affected versions and patch details below.
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 GHSA-2rvv-w9r2-rg7m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-2rvv-w9r2-rg7m by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
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.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
When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 10.0.0-M1&&< 10.0.0-M10 | 10.0.0-M10org.apache.tomcat.embed:tomcat-embed-core:10.0.0-M10 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 9.0.0&&< 9.0.40 | 9.0.40org.apache.tomcat.embed:tomcat-embed-core:9.0.40 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 8.5.0&&< 8.5.60 | 8.5.60org.apache.tomcat.embed:tomcat-embed-core:8.5.60 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 7.0.0&&< 7.0.107 | 7.0.107org.apache.tomcat.embed:tomcat-embed-core:7.0.107 |
Affected Products
tomcatapachedebian linuxdebianagile product lifecycle managementoracleDetection & 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 10.0.0-M10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2rvv-w9r2-rg7m is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
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.
In Red Hat OpenStack Platform's OpenDaylight, tomcat is disabled by default. Further, ODL deployments are not supported on untrusted administrator networks; even if tomcat is enabled, if random users can access it, this would be in an unsupported configuration. For this reason, the RHOSP impact has been reduced and…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Fuse 7.11 | tomcat | RHSA-2022:5532 |
| Red Hat JBoss Web Server 5 | tomcat | RHSA-2021:0495 |
| Red Hat JBoss Web Server 5.4 on RHEL 7 | jws5-tomcat-0:9.0.36-9.redhat_8.1.el7jws | RHSA-2021:0494 |
| Red Hat support for Spring Boot 2.3.10 | see advisory | RHSA-2021:3425 |
Frequently Asked Questions
Is GHSA-2rvv-w9r2-rg7m in your dependencies?
Find it across Maven, including transitive dependencies.