CVE-2026-87742: Quarkus-websockets-next: denial of service (oom) in quarkus-websockets-next via unbounded message buffering

Published Sep 9, 2026
·
Updated

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).

Other sources

Title: Denial of Service (OOM) in quarkus-websockets-next via unbounded message buffering Summary:

A Denial of Service vulnerability exists in the quarkus-websockets-next extension due to unbounded message buffering.The framework uses an unbounded queue and fails to apply read backpressure on the underlying network socket. An attacker can stream messages over a single connection faster than the application's handler can process them. This rapidly exhausts heap space, causing a java.lang.OutOfMemoryError that crashes the JVM.

Component: io.quarkus:quarkus-vertx-httpCWE: CWE-400, CWE-770 Scoring: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5/10) Affected versions: 3.27, 3.33

Credit: Michael Read (https://github.com/Michael-JRead)

— Red Hat

Affected Software

3 affected components
quarkus-websockets-next=3.27, =3.33
IBM Enterprise Build of Quarkus<=3.27.1 - 3.27.5.SP1
IBM Enterprise Build of Quarkus<=3.33.1 - 3.33.3.SP1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade io.quarkus:quarkus-websockets-next to a version that resolves this vulnerability.

    Fixed in 3.27
  2. Upgrade

    Upgrade io.quarkus:quarkus-websockets-next to a version that resolves this vulnerability.

    Fixed in 3.33

Event History

Sep 9, 2026
Data Sourced
via Red Hat·06:08 AM
DescriptionSeverityAffected Software
Sep 17, 2026
CVE Published
via MITRE·02:57 PM
Data Sourced
via MITRE·02:57 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Sep 23, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Who can exploit this issue?

Any remote attacker that can establish a WebSocket connection to an affected application can exploit it. No authentication or user interaction is required.

2

What conditions are required for exploitation?

The attacker must send messages over a single connection faster than the application’s handler can process them. The unbounded buffering and absence of read backpressure allow queued messages to consume heap memory.

3

What is the operational impact?

Heap exhaustion triggers a java.lang.OutOfMemoryError and can crash the JVM, causing denial of service. The provided scoring indicates no direct confidentiality or integrity impact.

4

Which versions are identified as affected?

The affected versions listed are 3.27 and 3.33.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203