Eclipse Jetty up to 9.4.59/10.0.27/11.0.27/12.0.32/12.1.6 Double Quote request smuggling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 5.68- |
Summary
A vulnerability labeled as problematic has been found in Eclipse Jetty up to 9.4.59/10.0.27/11.0.27/12.0.32/12.1.6. This affects an unknown part of the component Double Quote Handler. Executing a manipulation can lead to request smuggling. The identification of this vulnerability is CVE-2026-2332. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability has been found in Eclipse Jetty up to 9.4.59/10.0.27/11.0.27/12.0.32/12.1.6 and classified as problematic. This vulnerability affects an unknown part of the component Double Quote Handler. The manipulation with an unknown input leads to a request smuggling vulnerability. The CWE definition for the vulnerability is CWE-444. The product acts as an intermediary HTTP agent
(such as a proxy or firewall) in the data flow between two
entities such as a client and server, but it does not
interpret malformed HTTP requests or responses in ways that
are consistent with how the messages will be processed by
those entities that are at the ultimate destination. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-2332 since 02/11/2026. The exploitation appears to be difficult. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/14/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-22243). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
- 9.4.4
- 9.4.5
- 9.4.6
- 9.4.7
- 9.4.8
- 9.4.9
- 9.4.10
- 9.4.11
- 9.4.12
- 9.4.13
- 9.4.14
- 9.4.15
- 9.4.16
- 9.4.17
- 9.4.18
- 9.4.19
- 9.4.20
- 9.4.21
- 9.4.22
- 9.4.23
- 9.4.24
- 9.4.25
- 9.4.26
- 9.4.27
- 9.4.28
- 9.4.29
- 9.4.30
- 9.4.31
- 9.4.32
- 9.4.33
- 9.4.34
- 9.4.35
- 9.4.36
- 9.4.37
- 9.4.38
- 9.4.39
- 9.4.40
- 9.4.41
- 9.4.42
- 9.4.43
- 9.4.44
- 9.4.45
- 9.4.46
- 9.4.47
- 9.4.48
- 9.4.49
- 9.4.50
- 9.4.51
- 9.4.52
- 9.4.53
- 9.4.54
- 9.4.55
- 9.4.56
- 9.4.57
- 9.4.58
- 9.4.59
- 10.0.0
- 10.0.1
- 10.0.2
- 10.0.3
- 10.0.4
- 10.0.5
- 10.0.6
- 10.0.7
- 10.0.8
- 10.0.9
- 10.0.10
- 10.0.11
- 10.0.12
- 10.0.13
- 10.0.14
- 10.0.15
- 10.0.16
- 10.0.17
- 10.0.18
- 10.0.19
- 10.0.20
- 10.0.21
- 10.0.22
- 10.0.23
- 10.0.24
- 10.0.25
- 10.0.26
- 10.0.27
- 11.0.0
- 11.0.1
- 11.0.2
- 11.0.3
- 11.0.4
- 11.0.5
- 11.0.6
- 11.0.7
- 11.0.8
- 11.0.9
- 11.0.10
- 11.0.11
- 11.0.12
- 11.0.13
- 11.0.14
- 11.0.15
- 11.0.16
- 11.0.17
- 11.0.18
- 11.0.19
- 11.0.20
- 11.0.21
- 11.0.22
- 11.0.23
- 11.0.24
- 11.0.25
- 11.0.26
- 11.0.27
- 12.0.0
- 12.0.1
- 12.0.2
- 12.0.3
- 12.0.4
- 12.0.5
- 12.0.6
- 12.0.7
- 12.0.8
- 12.0.9
- 12.0.10
- 12.0.11
- 12.0.12
- 12.0.13
- 12.0.14
- 12.0.15
- 12.0.16
- 12.0.17
- 12.0.18
- 12.0.19
- 12.0.20
- 12.0.21
- 12.0.22
- 12.0.23
- 12.0.24
- 12.0.25
- 12.0.26
- 12.0.27
- 12.0.28
- 12.0.29
- 12.0.30
- 12.0.31
- 12.0.32
- 12.1.0
- 12.1.1
- 12.1.2
- 12.1.3
- 12.1.4
- 12.1.5
- 12.1.6
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.4
CNA Vector (eclipse): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Request smugglingCWE: CWE-444
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/11/2026 CVE reserved04/14/2026 Advisory disclosed
04/14/2026 VulDB entry created
04/14/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-2332 (🔒)
GCVE (CVE): GCVE-0-2026-2332
GCVE (VulDB): GCVE-100-357304
EUVD: 🔒
Entry
Created: 04/14/2026 13:45Updated: 04/14/2026 16:34
Changes: 04/14/2026 13:45 (61), 04/14/2026 16:34 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.