CVE-2026-2332: HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-2332 is a high-severity request smuggling flaw in Eclipse Jetty's HTTP/1.1 parsing. A specially malformed chunked request can make Jetty disagree with another HTTP component about where one request ends, potentially hiding a second request inside the connection.
Executive priority
Prioritize internet-facing Jetty applications and platforms using Red Hat-packaged Jetty. Treat this as high priority because request smuggling can bypass normal request boundaries, but current evidence here does not support claiming active exploitation.
Technical view
Jetty mishandles chunk extension quoted-string parsing by terminating at CRLF inside an unterminated quoted string instead of rejecting the request. The issue is classified as CWE-444 with CVSS 7.4. The listed affected package is Maven org.eclipse.jetty/jetty-http across Jetty 9.4.0, 10.0.0, 11.0.0, 12.0.0, and 12.1.0 lines.
Likely exposure
Exposure is most likely where Jetty directly handles HTTP/1.1 traffic, especially behind proxies, load balancers, or gateways that may parse malformed chunked requests differently. Confirm whether applications embed or depend on org.eclipse.jetty:jetty-http in the affected version lines.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation is network reachable and unauthenticated, but CVSS marks attack complexity high, consistent with request-smuggling conditions depending on multi-hop HTTP parsing behavior.
Researcher notes
The key parser behavior is CRLF termination inside a chunk-extension quoted string. Assess parser differentials only in controlled environments and avoid weaponized reproduction. The bundle does not provide fixed Jetty versions, so remediation status must be verified against vendor advisories.
Mitigation direction
Check Eclipse Jetty advisory GHSA-355h-qmc2-wpwf for fixed version guidance.
Apply relevant Red Hat RHSA updates where Jetty is supplied by Red Hat.
Inventory direct and transitive org.eclipse.jetty:jetty-http dependencies.
Reduce direct HTTP/1.1 exposure to vulnerable Jetty services where feasible.
Review proxy and gateway rules for rejection of malformed chunked requests.
Validation and detection
Search dependency manifests and SBOMs for org.eclipse.jetty:jetty-http.
Map each finding to Jetty 9.4.0, 10.0.0, 11.0.0, 12.0.0, or 12.1.0 lines.
Identify services where Jetty receives HTTP/1.1 through reverse proxies or load balancers.
Confirm vendor advisory status before declaring a version remediated.
Monitor logs for abnormal chunked requests and request-boundary anomalies.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-444: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
13Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-444 · source CWE mapping
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.