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.
{
"cna_assigner": "eclipse",
"cwe_ids": [
"CWE-770",
"CWE-789"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/19xxx/CVE-2026-19204.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "11.0.0"
},
{
"last_affected": "11.0.31"
},
{
"introduced": "10.0.0"
},
{
"last_affected": "10.0.31"
}
],
"source": "AFFECTED_FIELD"
}
]
}{
"extracted_events": [
{
"introduced": "12.1.0"
},
{
"last_affected": "12.1.11"
},
{
"introduced": "12.0.0"
},
{
"last_affected": "12.0.37"
}
],
"source": "AFFECTED_FIELD"
}