All reports
High

Apache Tomcat - WebSocket authentication header exposure

Affected versions

Affected versions
< 9.0.118
Fixed version
9.0.118
Affected versions
>= 11.0.0-M1, < 11.0.22
Fixed version
11.0.22
Affected versions
>= 10.1.0-M1, < 10.1.55
Fixed version
10.1.55
Affected versions
>= 11.0.0-M1, < 11.0.22
Fixed version
11.0.22
Affected versions
< 9.0.118
Fixed version
9.0.118
Affected versions
>= 10.1.0-M1, < 10.1.55
Fixed version
10.1.55
Affected versions
< 9.0.118
Fixed version
9.0.118
Affected versions
>= 11.0.0-M1, < 11.0.22
Fixed version
11.0.22
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
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
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-42498

Probability of exploitation in the next 30 days: 0.69%

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.2 to 9.0.117 Older, unsupported versions may also be affected

Description: If a WebSocket request was redirected after authentication, Tomcat's WebSocket client would present the most recent authentication header to the redirect target host.

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 lokerxx

Links