Allocation of Resources Without Limits or Throttling Affecting org.eclipse.jetty.websocket:jetty-websocket-core-common package, versions [,12.0.38)[12.1.0.alpha0,12.1.12)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGECLIPSEJETTYWEBSOCKET-19644206
- published8 Sept 2026
- disclosed7 Sept 2026
- creditUnknown
Introduced: 7 Sep 2026
NewCVE-2026-19204 (opens in a new tab)How to fix?
Upgrade org.eclipse.jetty.websocket:jetty-websocket-core-common to version 12.0.38, 12.1.12 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in its WebSocket frame parsing, where a frame carrying an unknown opcode bypasses the maximum frame size validation and its declared payload length is allocated before the opcode is validated. An attacker can exhaust the JVM heap by sending a WebSocket frame with an unknown opcode and a very large declared payload length. This requires WebSocket auto-fragmentation to be enabled and the attacker to be a connected WebSocket client.
Workaround
This vulnerability can be avoided by disabling WebSocket auto-fragmentation (setAutoFragment(false)), which removes the path that allocates the declared payload before the opcode is validated.