CVE-2026-15565

Description

A flaw was found in Undertow. A remote attacker can cause Out of Memory on websockets endpoint without authentication on any @ServerEndpoint class that has any @OnMessage method. This allows an attacker to cause Denial of Service attack without authentication and using only a standard WebSocket handshake.

Statement

A denial-of-service flaw rated IMPORTANT was found in the Undertow WebSocket (JSR-356) implementation used by Red Hat JBoss EAP and other Red Hat middleware products that ship the undertow-websockets-jsr component. A remote attacker can, without authentication, complete a standard WebSocket handshake against any deployed @ServerEndpoint class that declares an @OnMessage method and send oversized text messages, causing the server to buffer unbounded amounts of data in memory and resulting in an out-of-memory denial of service. The root cause is that the application-configured maxMessageSize limit is not enforced for text WebSocket messages: the internal buffered-text-message object is always created with no size limit, discarding the developer's configured value, and the accumulated size is not checked while data arrives asynchronously, so data is already fully held in memory before any size check runs. Red Hat rates this flaw as IMPORTANT with a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), consistent with the upstream CVE severity. The affected component ships in JBoss EAP 7 and JBoss EAP 8 and in the Red Hat build of Apache Camel for Spring Boot, where fixes are being pursued through the corresponding product maintenance streams. The EAP XP 6 stream is not affected because inline mitigations already exist in its code. For JBoss Data Grid 8.6 no fix is planned, and Red Hat JBoss Fuse 7 and Red Hat Single Sign-On 7 are out of support scope.

Mitigation

Option 1 — Server-wide configuration to disable websockets handshake:
  <!-- Remove <websockets/> from standalone.xml servlet-container -->
  <servlet-container name="default">
      <jsp-config/>
      <!-- <websockets/> ← remove this line entirely -->
  </servlet-container>
  isWebsocketsEnabled() returns false → no WebSocket upgrade accepted for any deployment.

Option 2 — Per-application configuration to disable websockets handshake:
  <!-- WEB-INF/jboss-web.xml inside the WAR -->
  <jboss-web>
      <enable-websockets>false</enable-websockets>
  </jboss-web>
  Only that specific WAR's @ServerEndpoint classes are not registered.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Confidentiality,Availability

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of the product's implicit security policy. This can often be used to subvert any other security service.

Availability

Technical Impact: Modify Memory; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)

Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the product into an infinite loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.