Service interruption via unbounded WebSocket fragment reassembly
Published Nov 11, 2026 · Updated Nov 11, 2026
Memory exhaustion in Cockpit's cockpit-ws service allows remote authenticated users to interrupt service via fragmented WebSocket messages. The process_contents_rfc6455 function in src/ws/websocketconnection.c appends fragments to a message buffer without checking the accumulated size. Upstream identifies post-authentication reachability, contrary to the supplied unauthenticated description; the evidence establishes memory exhaustion without identifying a specific crash or hang.
Summary
What happened
Memory exhaustion in Cockpit's cockpit-ws service allows remote authenticated users to interrupt service via fragmented WebSocket messages. The process_contents_rfc6455 function in src/ws/websocketconnection.c appends fragments to a message buffer without checking the accumulated size. Upstream identifies post-authentication reachability, contrary to the supplied unauthenticated description; the evidence establishes memory exhaustion without identifying a specific crash or hang.
The record
- CVE
- CVE-2026-91150
- Published
- Nov 11, 2026
- Updated
- Nov 11, 2026
- Vendor
- John Horne
- Product
- Red Hat Enterprise Linux 10
- Classifications
- T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 11, 2026CVE publishedPublication date reported by the CVE source.
- Nov 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us