Advisory record · GHSA-f525-44xv-f2qj

Apache Tomcat - HTTP/2 no-authority bypass of strict SNI validation

CVSS 9.8 CriticalCriticalEPSS 0.0075 · 55th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 26 Aug 2026, 00: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.20, <11.0.25 || >=10.1.53, <10.1.59 || >=9.0.115, <9.0.12111.0.25, 10.1.59, 9.0.121
org.apache.tomcat.embed:tomcat-embed-coreMaven>=11.0.20, <11.0.25 || >=10.1.53, <10.1.59 || >=9.0.115, <9.0.12111.0.25, 10.1.59, 9.0.121
Identifiers
GHSA-f525-44xv-f2qj · BIT-tomcat-2026-65637 · CVE-2026-65637
Weakness (CWE)
CWE-20
Tags
Published
26 Aug 2026
Updated
27 Oct 2026

Machine-written summary

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

Apache Tomcat versions 11.0.20 through 11.0.24, 10.1.53 through 10.1.57, and 9.0.115 through 9.0.120 are affected, as are the tomcat-coyote and tomcat-embed-core Maven packages in those ranges. The source gives few details on how the bypass is triggered or what an attacker can do after it. Users should upgrade to Tomcat 11.0.25, 10.1.59, or 9.0.121, which fix the issue.

Written 2 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
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0075, the 55th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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