dbcve.org
JettyApplication · Eclipse

CVE-2026-1605

HIGH · 7.5 CVSS v3.1 Published 2026-03-05
Fix available
A fix is available. Upgrade to 12.0.32 / 12.1.6 or later.
See remediation →
84/100
Remediation priority · High
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, 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 Content-Encoding: gzip, is processed and the corresponding response is not compressed. This happens because the JDK Inflater is allocated for decompressing the request, but it is not released because the release mechanism is tied to the compressed response. In this case, since the response is not compressed, the release mechanism does not trigger, causing the leak.

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 · high confidence

In Eclipse Jetty GzipHandler, the JDK Inflater allocated for decompressing gzipped HTTP requests is not released when the response is not compressed. The release mechanism is incorrectly tied to compressed responses, causing a resource leak that can lead to resource exhaustion over repeated requests.

MitigationUpgrade to Jetty version 12.0.32+ (for 12.0.x) or 12.1.0+ (for 12.1.x) which contains the patched release mechanism for the Inflater, or disable GzipHandler if upgrade is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:>= 12.0.0, < 12.0.32>= 12.1.0, < 12.1.6

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
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Jetty version
    Locate the jetty-version.jar file in the Jetty distribution, or examine the startup logs for the Jetty version string (format: 12.0.x or 12.1.x)
    Affected if Version is 12.0.0 through 12.0.31, or 12.1.0 through 12.1.5 (these are the vulnerable versions)
  2. Confirm GzipHandler is enabled
    Inspect the Jetty configuration files (such as start.d/*.ini, jetty.xml, or context XML files) for a GzipHandler bean definition or for the org.eclipse.jetty.server.handler.GzipHandler class being added to the server handlers
    Affected if GzipHandler is explicitly configured and active in the server configuration
  3. Determine response compression behavior
    Review the GzipHandler configuration to check if response compression is enabled. Look for mime-types, knownMethods, or other compression settings that would cause responses to be gzip-compressed. If these are not set or are configured to exclude the application's response types, responses will remain uncompressed
    Affected if GzipHandler is enabled but response compression is not configured, meaning responses remain uncompressed and the Inflater release mechanism does not trigger

The environment is affected if running a vulnerable Jetty 12.x version (12.0.0-12.0.31 or 12.1.0-12.1.5) with GzipHandler enabled and response compression disabled or not configured for the application's response types.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 12.0.32 / 12.1.6 or later
Fixed in 12.0.3212.1.6
Interim mitigation

Upgrade to Jetty version 12.0.32+ (for 12.0.x) or 12.1.0+ (for 12.1.x) which contains the patched release mechanism for the Inflater, or disable GzipHandler if upgrade is not immediately feasible.

Recommended fix High confidence

Jetty 12.0.32 or 12.1.6

  1. 1. Identify the current Jetty version in use by checking your project dependencies (e.g., pom.xml for Maven, build.gradle for Gradle)
  2. 2. If using Maven, update the jetty-version property or dependency version to 12.0.32 for 12.0.x branches, or 12.1.6 for 12.1.x branches
  3. 3. If using Gradle, update the Jetty dependency version accordingly
  4. 4. Rebuild and test the application to ensure the upgrade does not break existing functionality
  5. 5. Redeploy the updated application to the production environment
Caveat Upgrade within same major version should be low risk; however, test thoroughly as minor releases may include behavior changes

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

Fix this in Jetty Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1605 — 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-1605 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