CVE-2026-2332: HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
Noroxi assessment
Priority: Monitor (action score 36/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 70.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: jmc (AlmaLinux:9) 8.2.0-19.el9_8.2; jetty12 (Debian:14) 12.0.33-1; org.eclipse.jetty:jetty-http (Maven) 10.0.28, 11.0.29, 12.0.33.
Low priority for now. Upgrade to jmc (AlmaLinux:9) 8.2.0-19.el9_8.2; jetty12 (Debian:14) 12.0.33-1; org.eclipse.jetty:jetty-http (Maven) 10.0.28, 11.0.29, 12.0.33 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 14, 2026
- Updated
- Oct 26, 2026
- EPSS
- 1.3% · 70th percentile
- CWE
- CWE-444
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.1
- CNA · eclipse
- 7.4
- 1.7 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| eclipse | jetty | cpe:2.3:a:eclipse:jetty |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- eclipse jetty9.4.0 and later · before 9.4.60
- eclipse jetty10.0.0 and later · before 10.0.28
- eclipse jetty11.0.0 and later · before 11.0.28
- eclipse jetty12.0.0 and later · before 12.0.33
- eclipse jetty12.1.0 and later · before 12.1.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (eclipse). Independent of NVD's CPE analysis and usually ahead of it.
Eclipse Foundation Eclipse Jetty
- 12.1.0 and later · up to and including 12.1.6affected · semver
- 12.0.0 and later · up to and including 12.0.32affected · semver
- 11.0.0 and later · up to and including 11.0.28affected · semver
- 10.0.0 and later · up to and including 10.0.27affected · semver
- 9.4.0 and later · up to and including 9.4.59affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | jmc | before 8.2.0-19.el9_8.2 | 8.2.0-19.el9_8.2 |
| Debian:12 | jetty9 | from 0 | — |
| Debian:13 | jetty12 | from 0 | — |
| Debian:14 | jetty12 | before 12.0.33-1 | 12.0.33-1 |
| Maven | org.eclipse.jetty:jetty-http | from 10.0.0 · before 10.0.28 | 10.0.28 |
| Maven | org.eclipse.jetty:jetty-http | from 11.0.0 · before 11.0.29 | 11.0.29 |
| Maven | org.eclipse.jetty:jetty-http | from 12.0.0 · before 12.0.33 | 12.0.33 |
| Maven | org.eclipse.jetty:jetty-http | from 12.1.0 · before 12.1.7 | 12.1.7 |
| Maven | org.eclipse.jetty:jetty-http | from 9.4.0 · before 9.4.60 | 9.4.60 |
| openSUSE:Tumbleweed | jetty-minimal | before 9.4.58-4.1 | 9.4.58-4.1 |
| Red Hat:enterprise_linux:9::crb | jmc | before 0:8.2.0-19.el9_8.2 | 0:8.2.0-19.el9_8.2 |
| Red Hat:satellite_capsule:6.16::el8 | libsolv | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | libsolv-debuginfo | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | libsolv-debugsource | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | libsolv-demo-debuginfo | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | libsolv-tools-debuginfo | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | openvox-agent | before 0:8.24.1-3.el8sat | 0:8.24.1-3.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | openvox-server | before 0:8.14.1-1.el8sat | 0:8.14.1-1.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | perl-solv-debuginfo | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | python-pillow | before 0:12.3.0-1.el8pc | 0:12.3.0-1.el8pc |
| Red Hat:satellite_capsule:6.16::el8 | python-pillow-debugsource | before 0:12.3.0-1.el8pc | 0:12.3.0-1.el8pc |
| Red Hat:satellite_capsule:6.16::el8 | python-pyjwt | before 0:2.13.0-1.el8pc | 0:2.13.0-1.el8pc |
| Red Hat:satellite_capsule:6.16::el8 | python3-solv | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
| Red Hat:satellite_capsule:6.16::el8 | python3-solv-debuginfo | before 1:0.7.20-7.el8sat | 1:0.7.20-7.el8sat |
+36
Same product
eclipse: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34429For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the con60This week
- CVE-2021-28164In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm60This week
- CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem53Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-1605Mar 5, 2026 · In Eclipse Jetty, versions 12.0.0-12.0.31 and 12.1.0-12.0.5, class GzipHandler exposes a vulnerability when a compressed HTTP request, with 30Monitor
- ← EarlierCVE-2026-5795Apr 8, 2026 · In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable.29Monitor
- Later →CVE-2024-7708Jul 14, 2026 · For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:jmc | 8.2.0-19.el9_8.2 · AlmaLinux:9 | Package registry (OSV) |
| debian:jetty12 | 12.0.33-1 · Debian:14 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-http | 10.0.28 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-http | 11.0.29 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-http | 12.0.33 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-http | 12.1.7 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-http | 9.4.60 | Package registry (OSV) |
| opensuse:jetty-minimal | 9.4.58-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jmc | 0:8.2.0-19.el9_8.2 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:openvox-agent | 0:8.24.1-3.el9sat · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:openvox-server | 0:8.14.1-1.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:python-pyjwt | 0:2.13.0-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python3.12-pillow | 0:12.3.0-1.el9pc · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:python3.12-pillow-debuginfo | 0:12.3.0-1.el9pc · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:python3.12-pillow-debugsource | 0:12.3.0-1.el9pc · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:rubygem-faraday | 0:1.10.6-1.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:rubygem-katello | 0:4.20.0.7-1.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:rubygem-nokogiri | 0:1.17.2-3.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:rubygem-nokogiri-debuginfo | 0:1.17.2-3.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:rubygem-nokogiri-debugsource | 0:1.17.2-3.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| rocky linux:jmc | 0:8.2.0-19.el9_8.2 · Rocky Linux:9 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-12 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+150 d
- TodayOct 30, 2026+199 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- https://github.com/xclow3nreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:10175
- access.redhat.com/errata/RHSA-2026:14272
- access.redhat.com/errata/RHSA-2026:17668
- access.redhat.com/errata/RHSA-2026:20568
- access.redhat.com/errata/RHSA-2026:21773
- access.redhat.com/errata/RHSA-2026:22453
- access.redhat.com/errata/RHSA-2026:25089
- access.redhat.com/errata/RHSA-2026:50221
- access.redhat.com/errata/RHSA-2026:50222
- access.redhat.com/errata/RHSA-2026:50223
- access.redhat.com/errata/RHSA-2026:50263
- access.redhat.com/errata/RHSA-2026:60239
- access.redhat.com/errata/RHSA-2026:60246
- access.redhat.com/errata/RHSA-2026:60247
- access.redhat.com/errata/RHSA-2026:60248
- access.redhat.com/errata/RHSA-2026:60249
- access.redhat.com/errata/RHSA-2026:60250
- access.redhat.com/errata/RHSA-2026:60251
- access.redhat.com/errata/RHSA-2026:60252
Vendor advisories and official records. Exploit/PoC links are deliberately left out.