JVM crash via unbounded WebSocket message buffering
Published Sep 17, 2026 · Updated Sep 21, 2026
Resource exhaustion in quarkus-websockets-next allows remote attackers to crash the JVM by rapidly streaming WebSocket messages. The extension buffers messages without a bound or read backpressure when input arrives faster than the application processes it, exhausting Java heap space. Exploitation requires network access to an affected WebSocket endpoint and interrupts that Java service without reported data exposure or modification.
Summary
What happened
Resource exhaustion in quarkus-websockets-next allows remote attackers to crash the JVM by rapidly streaming WebSocket messages. The extension buffers messages without a bound or read backpressure when input arrives faster than the application processes it, exhausting Java heap space. Exploitation requires network access to an affected WebSocket endpoint and interrupts that Java service without reported data exposure or modification.
The record
- CVE
- CVE-2026-87742
- Published
- Sep 17, 2026
- Updated
- Sep 21, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat Enterprise Linux AI
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Get started