Advisory record · GHSA-gqp3-2cvr-x8m3

Apache Tomcat Improper Resource Shutdown or Release vulnerability

CVSS 7.5 HighEPSS 0.038 · 90th percentile

Published by the GitHub Advisory Database at 13 Aug 2025, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.tomcat:tomcat-coyoteMaven>=11.0.0-M1, <11.0.10 || >=10.1.0-M1, <10.1.44 || >=9.0.0.M1, <9.0.10811.0.10, 10.1.44, 9.0.108
org.apache.tomcat.embed:tomcat-embed-coreMaven>=11.0.0-M1, <11.0.10 || >=10.1.0-M1, <10.1.44 || >=9.0.0.M1, <9.0.10811.0.10, 10.1.44, 9.0.108
Identifiers
GHSA-gqp3-2cvr-x8m3 · BIT-tomcat-2025-48989 · CVE-2025-48989
Weakness (CWE)
CWE-404
Published
13 Aug 2025
Updated
13 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Tomcat versions 11.0.0-M1 through 11.0.9, 10.1.0-M1 through 10.1.43 and 9.0.0.M1 through 9.0.107 are vulnerable, affecting the tomcat-coyote and tomcat-embed-core packages. The source gives few details on how the attack is carried out, beyond that it is a "made you reset" attack, which is a type of HTTP/2 resource exhaustion. Upgrade to 11.0.10, 10.1.44 or 9.0.108, depending on the release line in use. The source does not list a workaround.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.038, the 90th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.