CVE intelligence and bounded remediation
CVE-2026-2332 — Eclipse Jetty security vulnerability
In Eclipse Jetty, the HTTP/1.1 parser is vulnerable to request smuggling when chunk extensions are used, similar to the "funky chunks" techniques outlined here: * https://w4ke.info/2025/06/18/funky-chunks.html * https://w4ke.info/2025/10/29/funky-chunks-2.html Jetty terminates chunk extension parsing at \r\n inside quoted strings instead of treating this as an error. POST / HTTP/1.1 Host: localhost Transfer-Encoding: chunked 1;ext="val X 0 GET /smuggled HTTP/1.1 ... Note how the chunk extension does not close the double quotes, and it is able to inject a smuggled request.
- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Published
- 2026-04-14
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-444
Affected products
- eclipse / jetty
Matched remediation archetype
HTTP request smuggling and message-boundary ambiguity
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory every proxy, CDN, gateway, load balancer, service mesh, and application server hop on affected request paths.
- Compare documented parsing and normalization behavior for message length, transfer coding, duplicate headers, and protocol translation.
- Identify connection reuse and which downstream services trust headers added by intermediaries.
Remediate safely
- Update affected intermediaries and origin servers and align them on a single standards-compliant request framing policy.
- Reject ambiguous length, transfer-coding, duplicate, malformed, and unsupported framing before forwarding.
- Normalize or remove hop-by-hop and identity headers at one controlled boundary and add multi-hop regression tests.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.