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

Uncontrolled Resource Consumption in Apache TomcatGHSA-53hp-jpwq-2jgq

HIGHFix: apache/tomcat@9434a44

GHSA-53hp-jpwq-2jgq is a high-severity (CVSS 7.5) vulnerability in org.apache.tomcat:tomcat. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Also known asBIT-tomcat-2020-11996CVE-2020-11996
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
2 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
26.7%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk
21.2%31.0%40.8%50.6%45.1%26.7%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-53hp-jpwq-2jgq 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

6 pkgs affected
☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕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

A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 10.0.0-M1&&< 10.0.0-M510.0.0-M5org.apache.tomcat:tomcat:10.0.0-M5
☕Mavenorg.apache.tomcat:tomcat≥ 9.0.0.M1&&< 9.0.359.0.35org.apache.tomcat:tomcat:9.0.35
☕Mavenorg.apache.tomcat:tomcat≥ 8.5.0&&< 8.5.558.5.55org.apache.tomcat:tomcat:8.5.55
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 10.0.0-M1&&< 10.0.0-M510.0.0-M5org.apache.tomcat.embed:tomcat-embed-core:10.0.0-M5
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 9.0.0.M1&&< 9.0.359.0.35org.apache.tomcat.embed:tomcat-embed-core:9.0.35
☕Mavenorg.apache.tomcat.embed:tomcat-embed-core≥ 8.5.0&&< 8.5.558.5.55org.apache.tomcat.embed:tomcat-embed-core:8.5.55

Affected Products

8 products · 46 configurations
Application
tomcatapache
≥ 9.0.0 && ≤ 9.0.35
2 versions
9.0.010.0.0
OS
ubuntu linuxcanonical
1 version
20.04
OS
debian linuxdebian
2 versions
9.010.0
Application
oncommand system managernetapp
2 versions
3.03.1.3
OS
leapopensuse
2 versions
15.115.2
Application
mysql enterprise monitororacle
≤ 8.0.21
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.tomcat:tomcat to 10.0.0-M5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-53hp-jpwq-2jgq is resolved across your whole dependency graph.

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

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

Red Hat OpenStack Platform's OpenDaylight will not be updated for this flaw because it was deprecated as of RHOSP14 and is only receiving security fixes for Important and Critical flaws. Apache Tomcat versions as shipped with Red Hat Enterprise Linux 6 and 7 are not affected by this flaw as it doesn't support HTTP/2…

ProductFixed inAdvisory
Red Hat Fuse 7.9tomcatRHSA-2021:3140
Red Hat JBoss Web Server 5tomcatRHSA-2020:5173
Red Hat JBoss Web Server 5.4 on RHEL 6jws5-jboss-logging-0:3.4.1-1.Final_redhat_00001.1.el6jwsRHSA-2020:5170
Red Hat support for Spring Boot 2.3.6tomcatRHSA-2021:0292
Text-Only RHOARsee advisoryRHSA-2020:5388

Frequently Asked Questions

A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.
O3 Security · Impact-Aware SCA

Is GHSA-53hp-jpwq-2jgq in your dependencies?

Find it across Maven, including transitive dependencies.

Uncontrolled Resource Consumption in Apache Tomcat