All reports
Critical

Apache Tomcat - HTTP/2 request headers not validated

Affected versions

Affected versions
>= 11.0.0-M1, < 11.0.22
Fixed version
11.0.22
Affected versions
>= 8.5.0, < 9.0.118
Fixed version
9.0.118
Affected versions
>= 10.1.0-M1, < 10.1.55
Fixed version
10.1.55
Affected versions
>= 10.1.0-M1, < 10.1.55
Fixed version
10.1.55
Affected versions
>= 8.5.0, < 9.0.118
Fixed version
9.0.118
Affected versions
>= 11.0.0-M1, < 11.0.22
Fixed version
11.0.22
Affected versions
>= 11.0.0-M1, < 11.0.22
Fixed version
11.0.22
Affected versions
>= 8.5.0, < 9.0.118
Fixed version
9.0.118
Affected versions
>= 10.1.0-M1, < 10.1.55
Fixed version
10.1.55
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-41293

Probability of exploitation in the next 30 days: 1.71%

FIRST EPSS · 2026-11-18

Description

Versions Affected: Apache Tomcat 11.0.0-M1 to 11.0.21 Apache Tomcat 10.1.0-M1 to 10.1.54 Apache Tomcat 9.0.0.M1 to 9.0.117 Older, unsupported versions may also be affected

Description: HTTP/2 request headers were not validated which may have triggered unexpected application behaviour if the application (quite reasonably) assumed that header value exposed through the Servlet API would be specification compliant.

Mitigation: Users of the affected versions should apply one of the following mitigations:

  • Upgrade to Apache Tomcat 11.0.22 or later

  • Upgrade to Apache Tomcat 10.1.55 or later

  • Upgrade to Apache Tomcat 9.0.118 or later

Credit: This issue was identified by Dawit Jeong (@dawitngoliath)

Links

Credits

  • sealbenb