Bug 2524165 (CVE-2026-73180) - CVE-2026-73180 tomcat: Apache Tomcat: Authenticated WebSocket session persists after HTTP session termination
Summary: CVE-2026-73180 tomcat: Apache Tomcat: Authenticated WebSocket session persist...
Keywords:
Status: NEW
Alias: CVE-2026-73180
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-25 22:11 UTC by OSIDB Bzimport
Modified: 2026-10-07 13:32 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:73981 0 None None None 2026-10-01 22:11:35 UTC
Red Hat Product Errata RHSA-2026:73982 0 None None None 2026-10-01 16:24:28 UTC
Red Hat Product Errata RHSA-2026:76952 0 None None None 2026-10-07 13:32:42 UTC
Red Hat Product Errata RHSA-2026:76956 0 None None None 2026-10-07 13:31:12 UTC

Description OSIDB Bzimport 2026-08-25 22:11:19 UTC 
Insufficient Session Expiration vulnerability in Apache Tomcat meant that if the session ID for an authenticated HTTP session was changed after a WebSocket connection had been established under that authenticated HTTP session, the WebSokcet session would not be closed as required by the Jakarta WebSocket specification when the HTTP session ended.



This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120.



The following versions were EOL at the time the CVE was created but are 
known to be affected: from 8.5.0 through 8.5.100, from 7.0.43 through 7.0.109. Other unsupported versions may also be affected.



Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121, which fix the issue.
Comment 2 Jon Orris 2026-10-01 16:24:27 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 6.2.5

Via RHSA-2026:73982 https://access.redhat.com/errata/RHSA-2026:73982
Comment 3 Jon Orris 2026-10-01 22:11:34 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 6.2 on RHEL 10
  Red Hat JBoss Web Server 6.2 on RHEL 8
  Red Hat JBoss Web Server 6.2 on RHEL 9

Via RHSA-2026:73981 https://access.redhat.com/errata/RHSA-2026:73981
Comment 4 Jon Orris 2026-10-07 13:31:11 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 7.0.2

Via RHSA-2026:76956 https://access.redhat.com/errata/RHSA-2026:76956
Comment 5 Jon Orris 2026-10-07 13:32:41 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 7.0 on RHEL 10
  Red Hat JBoss Web Server 7.0 on RHEL 8
  Red Hat JBoss Web Server 7.0 on RHEL 9

Via RHSA-2026:76952 https://access.redhat.com/errata/RHSA-2026:76952
Note You need to log in before you can comment on or make changes to this bug.