# CVE-2026-1605: The Eclipse Jetty Server Artifact has a Gzip request memory leak > Attackers can cause resource exhaustion and denial of service by sending compressed requests that trigger a memory leak in the GzipHandler. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Mar 2026 - **Updated:** 14 Sep 2026 - **Also known as:** CLEANSTART-2026-DU44734, CLEANSTART-2026-GS83780, CLEANSTART-2026-KO17168, CLEANSTART-2026-MN49716, CLEANSTART-2026-UT17320, DEBIAN-CVE-2026-1605, ECHO-7ace-751a-c022, GHSA-xxh7-fcf3-rj7f, MINI-2cgj-jqwc-cvqw, MINI-2mxw-gx26-ff3f, MINI-3jpp-jv5j-599q, MINI-67g7-5gjf-894v, MINI-6v66-8x56-3xm6, MINI-78w5-q2rc-m3jm, MINI-7jp3-g94q-frxp, MINI-8h9c-77px-9333, MINI-8rq9-j2rh-hm6q, MINI-949f-gchr-jw2v, MINI-9684-356f-4w68, MINI-9mfj-wmf3-c4gq, MINI-9rhj-2pc8-3g6m, MINI-9wfh-x332-hvc6, MINI-cjhh-r6gp-9ppr, MINI-cw9g-75f8-vxpr, MINI-f7cg-mj7j-j8f7, MINI-fp37-j59r-69f8, MINI-fwhr-8jc4-vpw2, MINI-gqp9-6cfr-q83h, MINI-h6cm-gwf7-h5c9, MINI-hjmj-m536-r82w, MINI-j6gr-cp9m-f949, MINI-m595-2c84-fp7g, MINI-m7p5-f47c-54fh, MINI-mw8j-gq5h-x4cx, MINI-ph27-wr67-cxhr, MINI-qvfh-x2qh-x4pp, MINI-rjh6-9f4c-cfm2, MINI-wf7m-j44h-m7q7, MINI-wh59-f948-mg3r, MINI-x364-vjv5-3978, ROOT-APP-MAVEN-CVE-2026-1605, UBUNTU-CVE-2026-1605 ## What is CVE-2026-1605? CVE-2026-1605 is a high-severity denial of service vulnerability in Eclipse Jetty, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime), CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-1605? 4 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0 | 12.0.32 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0 | 12.0.32 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.1.0 | 12.1.6 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.1.0 | 12.1.6 | Products: Eclipse Jetty. ## How do I fix CVE-2026-1605? Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 12.0.32 or 12.1.6. ## Is CVE-2026-1605 being exploited? There is no known exploitation of CVE-2026-1605 in the wild and no public exploit code. ## Other vulnerabilities in Eclipse Jetty - [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8) - [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4) - [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8) - [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7) - [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-1605 and fix it if it is affected. What it is: CVE-2026-1605 is a high-severity denial of service vulnerability in Eclipse Jetty, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-1605 in the wild and no public exploit code. Affected packages and fixed versions: - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0; fixed in 12.0.32 - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0; fixed in 12.0.32 - org.eclipse.jetty:jetty-server (Maven): affected from 12.1.0; fixed in 12.1.6 - org.eclipse.jetty:jetty-server (Maven): affected from 12.1.0; fixed in 12.1.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-1605/ (Markdown: https://insights.sbomify.com/CVE-2026-1605/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1605 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1605 - OSV: https://osv.dev/vulnerability/CVE-2026-1605 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-1605/ Summaries are generated and may contain mistakes; the official description above is the record.