Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2021-24122 — tomcat-embed-core

MEDIUMFix: apache/tomcat@7f004ac

CVE-2021-24122 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.

Information Disclosure in Apache Tomcat

Also known asBIT-tomcat-2021-24122GHSA-2rvv-w9r2-rg7m
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Sep 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
22.9%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-24122 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected
☕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-core

Real-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

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 10.0.0-M1&&< 10.0.0-M1010.0.0-M10org.apache.tomcat.embed:tomcat-embed-core:10.0.0-M10
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 9.0.0&&< 9.0.409.0.40org.apache.tomcat.embed:tomcat-embed-core:9.0.40
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 8.5.0&&< 8.5.608.5.60org.apache.tomcat.embed:tomcat-embed-core:8.5.60
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 7.0.0&&< 7.0.1077.0.107org.apache.tomcat.embed:tomcat-embed-core:7.0.107

Affected Products

3 products · 42 configurations
Application
tomcatapache
≥ 9.0.1 && ≤ 9.0.39
2 versions
9.0.010.0.0
OS
debian linuxdebian
1 version
9.0
Application
agile product lifecycle managementoracle
2 versions
9.3.39.3.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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 CVE-2021-24122 is resolved across your whole dependency graph.

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

Red HatModerate

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…

ProductFixed inAdvisory
Red Hat Fuse 7.11tomcatRHSA-2022:5532
Red Hat JBoss Web Server 5tomcatRHSA-2021:0495
Red Hat JBoss Web Server 5.4 on RHEL 7jws5-tomcat-0:9.0.36-9.redhat_8.1.el7jwsRHSA-2021:0494
Red Hat support for Spring Boot 2.3.10see advisoryRHSA-2021:3425

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2021-24122 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2021-24122: tomcat-embed-core — Fixed in 10.0.0-M10