Skip to main content
VulnerabilityPublished Updated

CVE-2026-86350: Apache Tomcat · Regression in fix for CVE-2026-41293 can trigger request header mix-up

Affects tomcatSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-86350· Critical 9.1

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

Data as of 17 Nov 2026, 16:05 UTC

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

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 or 9.0.122.

Affected software

ProductAffectedFixed in
Bitnamitomcatpkg:bitnami/tomcatOther threatsAffected
  • >=9.0.118 <9.0.122
  • >=10.1.55 <10.1.60
  • >=11.0.22 <11.0.26
Fixed in
  • 9.0.122
  • 10.1.60
  • 11.0.26

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

AI-suggested

Users should upgrade affected Apache Tomcat versions to 9.0.122, 10.1.60, or 11.0.26, where the issue is fixed. Since a patch is available, applying these updates is the recommended remediation.

Description

A regression in the fix for CVE-2026-41293 in Apache Tomcat introduces an HTTP/2 request/response smuggling vulnerability that can cause request header mix-up. This affects Apache Tomcat versions from 9.0.118 through 9.0.121, 10.1.55 through 10.1.59, and 11.0.22 through 11.0.25. The issue is resolved in versions 9.0.122, 10.1.60, and 11.0.26.

References

Community reviews

Loading reviews…