dbcve.org
JettyApplication · Eclipse

CVE-2026-2332

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 9.4.60 / 10.0.28 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 2mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JettyApplication
Affected:>= 9.4.0, < 9.4.60>= 10.0.0, < 10.0.28>= 11.0.0, < 11.0.28>= 12.0.0, < 12.0.33>= 12.1.0, < 12.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.4.60 / 10.0.28 / 11.0.28 or later
Fixed in 9.4.6010.0.2811.0.28
Recommended fix High confidence

Jetty 9.4.60+ / 10.0.28+ / 11.0.28+ / 12.0.33+ (match your current major.minor version)

  1. 1. Identify all applications and services using Eclipse Jetty within the affected version ranges (9.4.0-9.4.59, 10.0.0-10.0.27, 11.0.0-11.0.27, 12.0.0-12.0.32)
  2. 2. Review dependency management files (pom.xml, build.gradle, package.json, etc.) to find Jetty dependencies
  3. 3. Update Jetty dependency version to the appropriate fixed release for your major version line
  4. 4. For Jetty 9.4.x: upgrade to version 9.4.60 or later
  5. 5. For Jetty 10.0.x: upgrade to version 10.0.28 or later
  6. 6. For Jetty 11.0.x: upgrade to version 11.0.28 or later
  7. 7. For Jetty 12.0.x: upgrade to version 12.0.33 or later
  8. 8. Rebuild and test applications to ensure compatibility with the new Jetty version
Caveat Minor release upgrades within the same major version typically have minimal breaking changes; however, review Jetty release notes for any behavioral changes between your current version and the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2332 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data