CVE-2026-19204

NameCVE-2026-19204
DescriptionA 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.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
jetty12 (PTS)trixie (security), trixie12.0.17-3.1~deb13u1vulnerable
forky12.0.33-1vulnerable
sid12.0.40-1fixed
jetty9 (PTS)bookworm, bookworm (security)9.4.57-1.1~deb12u1fixed
trixie (security), trixie9.4.57-1.1~deb13u1fixed
forky, sid9.4.58-2fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
jetty12source(unstable)12.0.39-1
jetty9source(unstable)(not affected)

Notes

- jetty9 <not-affected> (Only affects 10.x and later)
https://github.com/jetty/jetty.project/security/advisories/GHSA-85fq-fc5f-7j7g

Search for package or bug name: Reporting problems