← Back to results
Vulnerability record · public intelligence
CVE-2026-19204
HIGH
CVE-2026-19204
Published Sep 7, 2026 · Updated Nov 3, 2026
Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood0.45%
QFinch risk scoreNot available
Original summary
Normalized public record · Updated Nov 3, 2026
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.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
FIRST-EPSSCVE-LIST-V5
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Sep 7, 2026 · Last refreshed Nov 3, 2026