CVE-2026-19204
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.7
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- EPSS probability
- 0.29%
- CWE
- CWE-770, CWE-789
- Published
- 2026-09-07
- Last modified
- 2026-09-08
Affected products
- Eclipse Foundation Eclipse Jetty
- Eclipse Foundation Eclipse Jetty
- Eclipse Foundation Eclipse Jetty
- Eclipse Foundation Eclipse Jetty
Weakness type
Related vulnerabilities
- CVE-2026-45769 — ikev2: unbounded client transform storage can lead to resource exhaustion
- CVE-2026-45768 — Suricata ldap: unbounded responses per transaction can lead to resource exhaustion
- CVE-2026-45766 — Suricata nfs: unbounded stateful structures can lead to resource exhaustion
- CVE-2026-45765 — Suricata dnp3: unbounded reassembly can lead to resource exhaustion
- CVE-2026-88012 — Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded
- CVE-2026-45763 — Suricata lua: sandbox allocation limit not enforced for new allocations
- CVE-2026-88878 — Traefik v2.8.2 through v3.6 HTTP/3 Timeout Bypass
- CVE-2026-87011 — Open WebUI: Unauthenticated requests can stall the server via uncached OIDC fetches in back-channel logout