Skip to main content
VulnerabilityPublished Updated

CVE-2026-76183: Apache Tomcat · Bypass of security constraints for WebSocket endpoints

Affects tomcatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-76183· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical · fixed in 11.0.26 : patch tomcat as a priority.

Data as of 17 Nov 2026, 16:06 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 11.0.26, 10.1.60, 9.0.122 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade tomcat to 11.0.26, 10.1.60, 9.0.122 or 9.0.45.

Affected software

ProductAffectedFixed in
Bitnamitomcatpkg:bitnami/tomcatOther threatsAffected
  • >=7.0.43 <9.0.45
  • >=10.1.0 <10.1.60
  • >=11.0.0 <11.0.26
  • >=9.0.0 <9.0.122
Fixed in
  • 9.0.45
  • 10.1.60
  • 11.0.26
  • 9.0.122

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Tomcat to versions 11.0.26, 10.1.60, 9.0.122, or 9.0.45 or later, which contain fixes for this vulnerability. No other mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in Apache Tomcat allows bypassing security constraints on WebSocket endpoints via an authentication bypass by alternate name. This affects multiple versions across Tomcat 7, 8.5, 9, 10, and 11 branches. The issue is fixed in versions 11.0.26, 10.1.60, 9.0.122, and 9.0.45. Users should upgrade to these versions to mitigate the risk.

References

Community reviews

Loading reviews…