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.

Attack Vector Network

Attack Complexity Low

Privileges Required None

Attack Requirements None

User Interaction None

Vulnerable System Confidentiality Impact None

Vulnerable System Integrity Impact None

Vulnerable System Availability Impact High

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00293.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
Eclipse Foundation Eclipse Jetty unaffected
Version Status Constraints
12.1.0 affected ≤ 12.1.11
12.0.0 affected ≤ 12.0.37
11.0.0 affected ≤ 11.0.31
10.0.0 affected ≤ 10.0.31

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

Vendors Products
Eclipse Subscribe
Jetty Subscribe

Project Subscriptions

Vendors Products
Eclipse Subscribe
Jetty Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://github.com/jetty/jetty.project/security/advisories/GHSA-85fq-fc5f-7j7g cve-icon cve-icon
History

Mon, 07 Sep 2026 13:45:00 +0000

Type Values Removed Values Added
Title Jetty WebSocket Frame Memory Exhaustion via Unknown Opcode and Large Payload
First Time appeared Eclipse
Eclipse jetty
Vendors & Products Eclipse
Eclipse jetty

Mon, 07 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
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.
Weaknesses CWE-770
CWE-789
References
Metrics cvssV4_0

{'score': 8.7, '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'}

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published:

Updated: 2026-09-07T10:19:24.186Z

Reserved: 2026-08-07T07:33:05.744Z

Link: CVE-2026-19204

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-09-07T11:17:20.600

Modified: 2026-09-08T14:15:01.243

Link: CVE-2026-19204

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-07T13:30:16Z

Weaknesses