Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4

Jetty has HTTP Request Smuggling via Chunked Extension Quoted-String Parsing

CVE-2026-2332GHSA-355h-qmc2-wpwf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.eclipse.jetty:jetty-http 12.1.7, 12.0.33, 11.0.29, 10.0.28, 9.4.60), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.eclipse.jetty:jetty-http

    Affected
    >= 12.1.0, <= 12.1.6>= 12.0.0, <= 12.0.32>= 10.0.0, <= 10.0.27>= 9.4.0, <= 9.4.59>= 11.0.0, <= 11.0.28
    Fixed in
    11.0.29, 9.4.60, 12.0.33, 12.1.7, 10.0.28

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-2332: 1.31% estimated exploitation activity in the next 30 days; percentile 70.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description (as reported) Jetty incorrectly parses quoted strings in HTTP/1.1 chunked transfer encoding extension values, enabling request smuggling attacks. Background This vulnerability is a new variant discovered while researching the "Funky Chunks" HTTP request smuggling techniques: - https://w4ke.info/2025/06/18/funky-chunks.html - https://w4ke.info/2025/10/29/funky-chunks-2.html The original research tested various chunk extension parsing differentials but did not test quoted-string handling within extension values. Technical Details RFC 9112 Section 7.1.1 defines chunked transfer encoding: RFC 9110 Section 5.6.4 defines quoted-string: A quoted-string continues until the closing DQUOTE, and \r\n sequences are not permitted within the quotes. Vulnerability Jetty terminates chunk header parsing at \r\n inside quoted strings instead of treating this as an error. Expected (RFC compliant): Actual (jetty): Proof of Concept Result: Server returns 2 HTTP responses from a single TCP…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-355h-qmc2-wpwf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-2332

Advisory: Jetty has HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
IDs: CVE-2026-2332, GHSA-355h-qmc2-wpwf
Record: https://patchnext.com/advisories/cve-2026-2332 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jetty:jetty-http 12.1.7, 12.0.33, 11.0.29, 10.0.28, 9.4.60. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jetty:jetty-http: affected >= 12.1.0, <= 12.1.6; >= 12.0.0, <= 12.0.32; >= 10.0.0, <= 10.0.27; >= 9.4.0, <= 9.4.59; >= 11.0.0, <= 11.0.28; fixed in 11.0.29, 9.4.60, 12.0.33, 12.1.7, 10.0.28

## Suggested inspection (read-only)
- Maven org.eclipse.jetty:jetty-http: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jetty:jetty-http.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-355h-qmc2-wpwf (GitHub-reviewed advisory GHSA-355h-qmc2-wpwf lists affected ranges: Maven org.eclipse.jetty:jetty-http >=12.1.0 =12.0.0 =10.0.0 =9.4.0 =11.0.0 <=11.0.28)

Commands are suggestions: review each one before running it.

Loading voting…