Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven

CVE-2026-2332

HIGH

CVE-2026-2332 is a high-severity (CVSS 7.4) vulnerability in org.eclipse.jetty:jetty-http. O3 Security confirms whether CVE-2026-2332 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

HTTP Request Smuggling via Chunked Extension Quoted-String Parsing

Also known asGHSA-355h-qmc2-wpwf
Published
Apr 14, 2026
Updated
Aug 7, 2026
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed

Blast Radius

5 pkgs affected
☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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:

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.

Affected Packages

5 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.eclipse.jetty:jetty-http≥ 12.1.0&&< 12.1.712.1.7
☕Mavenorg.eclipse.jetty:jetty-http≥ 12.0.0&&< 12.0.3312.0.33
☕Mavenorg.eclipse.jetty:jetty-http≥ 11.0.0No fix
☕Mavenorg.eclipse.jetty:jetty-http≥ 10.0.0No fix
☕Mavenorg.eclipse.jetty:jetty-http≥ 9.4.0No fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.eclipse.jetty:jetty-http to 12.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2332 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-2332 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-2332. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-2332 in your dependencies?

O3 detects CVE-2026-2332 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works