HighGHSA-53hp-jpwq-2jgqBIT-tomcat-2020-11996CVE-2020-11996

Uncontrolled Resource Consumption in Apache Tomcat

Published 9 Feb 2022 · Updated 11 Jun 2026

Is your project on an affected org.apache.tomcat:tomcat?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=10.0.0-M1 <10.0.0-M5
Fixed in
10.0.0-M5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=10.0.0-M5 -DforceVersion=true
Affected
>=9.0.0.M1 <9.0.35
Fixed in
9.0.35
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=9.0.35 -DforceVersion=true
Affected
>=8.5.0 <8.5.55
Fixed in
8.5.55
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=8.5.55 -DforceVersion=true
Affected
>=10.0.0-M1 <10.0.0-M5
Fixed in
10.0.0-M5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=10.0.0-M5 -DforceVersion=true
Affected
>=9.0.0.M1 <9.0.35
Fixed in
9.0.35
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=9.0.35 -DforceVersion=true
Affected
>=8.5.0 <8.5.55
Fixed in
8.5.55
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=8.5.55 -DforceVersion=true

Details

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.

Is GHSA-53hp-jpwq-2jgq in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.tomcat:tomcat, and gives you the command that fixes it.

More advisories for org.apache.tomcat:tomcat

  • CriticalCVE-2026-65905Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability · 26 Aug 2026
  • CriticalCVE-2026-65182Apache Tomcat has an Improper Access Control, Incorrect Authorization vulnerability · 26 Aug 2026
  • CriticalCVE-2026-68525Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability · 26 Aug 2026
  • CriticalCVE-2026-55276Apache Tomcat has an Always-Incorrect Control Flow Implementation vulnerability · 29 Jun 2026
  • HighCVE-2026-55957Apache Tomcat has a Missing Critical Step in Authentication vulnerability · 29 Jun 2026
  • HighCVE-2026-53404Apache Tomcat's rewrite valve has an Always-Incorrect Control Flow Implementation vulnerability · 29 Jun 2026
All 168 advisories for org.apache.tomcat:tomcat

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.