8.7
High
CVE-2026-19204 A client may send a WebSocket frame with an unknown opcode and a very large declared payload length, causing Jetty to…
Description
A client may send a WebSocket frame with an unknown opcode and a very large declared payload length, causing Jetty to attempt a large memory allocation and potentially exhaust the JVM heap. This occurs when auto-fragmentation is enabled, as unknown opcodes bypass the normal maximum frame size handling and payload allocation occurs before the opcode is validated.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Eclipse Jetty 12.1 | 12.1.0 → 12.1.11 | No fix stated |
| Eclipse Jetty 12.0 | 12.0.0 → 12.0.37 | No fix stated |
| Eclipse Jetty 11.0 | 11.0.0 → 11.0.31 | No fix stated |
| Eclipse Jetty 10.0 | 10.0.0 → 10.0.31 | No fix stated |
References
- github.com github.com
Timeline
- Published
- Last modified
Other CVEs of Eclipse Jetty
The 16 CVEs of Eclipse Jetty →
CVE-2026-18661
In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec…
8.8
High
CVE-2026-77711
When Jetty's `HttpClient` make a request to a server through a forward proxy, the server may reply with a 407 (Proxy…
8.2
High
CVE-2026-76184
In Eclipse Jetty, HttpClient may receive a redirect of the form: ``` /secure/../evil ``` If an attacker is able to…
8.2
High
CVE-2026-76182
In Eclipse Jetty, `TryPathsHandler` and `TryFilesFilter` can be configured to forward requests to template URIs such…
6.9
Medium