# The Eclipse Jetty Server Artifact has a Gzip request memory leak

Advisory record · `GHSA-xxh7-fcf3-rj7f`

- **Identifiers:** `GHSA-xxh7-fcf3-rj7f` · `CVE-2026-1605`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-401](https://cwe.mitre.org/data/definitions/401.html) · [CWE-772](https://cwe.mitre.org/data/definitions/772.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 5 Mar 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Mar 2026, 21:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.eclipse.jetty:jetty-server` (Maven): affected `>=12.1.0, <12.1.6 || >=12.0.0, <12.0.32`; fixed in `12.1.6`, `12.0.32`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Eclipse Jetty's jetty-server (org.eclipse.jetty:jetty-server) versions 12.0.0 up to 12.0.32 and 12.1.0 up to 12.1.6 are affected, per the affected ranges; fixed versions are 12.0.32 and 12.1.6. When GzipHandler receives a request with gzip Content-Encoding and the response is not gzip-encoded, inflater objects are not released, leaking native memory. A remote client can send such requests repeatedly to cause off-heap out-of-memory errors and crash the JVM. Upgrade to 12.0.32 or 12.1.6; as a workaround, disable GzipHandler.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (eclipse)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0074, the 55th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 5 Mar 2026, 09:41 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f)
- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xxh7-fcf3-rj7f)

## Sources

- [GitHub Advisory Database: GHSA-xxh7-fcf3-rj7f](https://github.com/advisories/GHSA-xxh7-fcf3-rj7f)
- [OSV: GHSA-xxh7-fcf3-rj7f](https://osv.dev/vulnerability/GHSA-xxh7-fcf3-rj7f)
- <https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-1605>
- <https://github.com/jetty/jetty.project/issues/14260>
- <https://github.com/jetty/jetty.project>
- <https://gitlab.eclipse.org/security/cve-assignment/-/issues/79>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xxh7-fcf3-rj7f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xxh7-fcf3-rj7f/>. Everything for agents: <https://agentprime.io/llms.txt>.