Answer in brief
CVE-2026-87742 records a High severity (CVSS 7.5) vulnerability in Quarkus-websockets-next: denial of service (oom) in quarkus-websockets-next via unbounded message buffering. The current sources do not mark it as known exploited. The current feed maps Red Hat/exploit-intelligence/agent-client-rhel9 (generic), Red Hat/rhelai3/bootc-cuda-rhel9 (generic), Red Hat/rhelai3/bootc-gaudi-rhel9 (generic), Red Hat/rhelai3/bootc-rocm-rhel9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/exploit-intelligence/agent-client-rhel9 (generic), Red Hat/rhelai3/bootc-cuda-rhel9 (generic), Red Hat/rhelai3/bootc-gaudi-rhel9 (generic), Red Hat/rhelai3/bootc-rocm-rhel9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/exploit-intelligence/agent-client-rhel9generic | * | Not reported |
| Red Hat/rhelai3/bootc-cuda-rhel9generic | * | Not reported |
| Red Hat/rhelai3/bootc-gaudi-rhel9generic | * | Not reported |
| Red Hat/rhelai3/bootc-rocm-rhel9generic | * | Not reported |
| Red Hat/rhelai3/disk-image-cuda-rhel9generic | * | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
A flaw was found in quarkus-websockets-next. This vulnerability allows a remote attacker to cause a Denial of Service (DoS) by streaming messages over a single connection faster than the application can process them. Due to unbounded message buffering and a lack of read backpressure, this rapidly exhausts heap space, leading to a java.lang.OutOfMemoryError that crashes the Java Virtual Machine (JVM).
Quoted source text, attributed separately from HOL analysis.