Advisory record · GHSA-vvw4-rfwf-p6hx

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

CVSS 7.5 HighCriticalEPSS 0.25 · 97th percentile

Critical, because:

  • CVSS score 7.5 (7.0 or more) and EPSS 0.25 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 9 Feb 2022, 22:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.tomcat:tomcat-coyoteMaven>=10.0.0-M1, <10.0.0-M10 || >=9.0.0-M1, <9.0.40 || >=8.5.0, <8.5.6010.0.0-M10, 9.0.40, 8.5.60
Identifiers
GHSA-vvw4-rfwf-p6hx · BIT-tomcat-2020-17527 · CVE-2020-17527
Weakness (CWE)
CWE-200
Published
9 Feb 2022
Updated
11 Mar 2024

Machine-written summary

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

Apache Tomcat's tomcat-coyote package, versions 10.0.0-M1 to 10.0.0-M9, 9.0.0-M1 to 9.0.39, and 8.5.0 to 8.5.59, can reuse an HTTP request header value from a previous stream on an HTTP/2 connection for a later stream. The source describes this as most likely causing an error and closing the connection, but it could also leak information between requests. Upgrade tomcat-coyote to 10.0.0-M10, 9.0.40, or 8.5.60.

Written 8 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:H/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.25, the 97th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 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.