# CVE-2026-10051: Eclipse Jetty: Cross-Request Leakage for trailers on HTTP/1.1 keep-alive connections > Attackers can leak HTTP trailer headers from previous requests on the same connection, exposing sensitive data to subsequent clients. - **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Jul 2026 - **Updated:** 14 Jul 2026 - **Also known as:** CLEANSTART-2026-CI10932, CLEANSTART-2026-EB27094, CLEANSTART-2026-LD18869, CLEANSTART-2026-LO54000, CLEANSTART-2026-PE66600, CLEANSTART-2026-QJ10298, CLEANSTART-2026-RP24727, CLEANSTART-2026-VU71113, DEBIAN-CVE-2026-10051, ECHO-1dd7-0ea6-3959, GHSA-f4v5-65jj-pcr2, MINI-3p9w-r96r-g7r5, MINI-3r7w-f684-xxhr, MINI-4cfj-wq8x-cgg8, MINI-4m45-36hj-3346, MINI-4r8p-5hhw-mf6v, MINI-5jfx-wg6m-rwwp, MINI-5rgq-8rg8-cf78, MINI-65w3-5jrx-cg87, MINI-6c32-pv96-rm8q, MINI-6j69-q5hg-hc8f, MINI-6qpp-8m55-hv67, MINI-7gf8-cmj4-r354, MINI-7wmh-32jq-hfpw, MINI-84cc-qpvh-j79j, MINI-85x9-3w2j-r2vx, MINI-8pxx-3w6h-h94r, MINI-8wqm-qmp7-74w9, MINI-9h62-x8w2-7ghr, MINI-9m3f-c848-mw89, MINI-9v99-xqp7-v896, MINI-9vhf-qfh3-mjv5, MINI-cw6g-gmfq-6gr5, MINI-f4r4-3336-rwg3, MINI-fmv3-8428-46jg, MINI-g646-fh2r-wjwg, MINI-g673-mxfm-cvww, MINI-g72f-xgqg-mc75, MINI-gm5h-5vgv-gf3w, MINI-h3qj-2549-4rx8, MINI-hj8w-wwjf-493w, MINI-hxfw-vvq3-r2p2, MINI-j2vw-cv96-fc8q, MINI-j7xr-32wm-r2j7, MINI-j8wx-9m66-rj37, MINI-jhvr-358w-j78c, MINI-jj3p-jvp5-99rh, MINI-m793-4v22-5hv6, MINI-mhv7-2mc3-42rj, MINI-p6h4-xqq8-f29w, MINI-q5hc-6m85-35xw, MINI-qpv2-g76c-c388, MINI-r6x2-24pc-gcph, MINI-rpgg-fxhv-4m2r, MINI-vpph-5f24-7325, ROOT-APP-MAVEN-CVE-2026-10051, UBUNTU-CVE-2026-10051 ## What is CVE-2026-10051? CVE-2026-10051 is a medium-severity vulnerability in Eclipse Jetty, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In Eclipse Jetty, a first HTTP/1.1 request with trailers causes the server to retain the trailers in subsequent requests performed over the same connection. Subsequent request that do not have trailers report the trailers of the first request. Subsequent request that do have trailers report the union of trailers of the first request and the current request. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-10051? 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.36 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0 | 12.0.36 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.1.0 | 12.1.10 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.1.0 | 12.1.10 | Products: Eclipse Jetty. ## How do I fix CVE-2026-10051? Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 12.0.36 or 12.1.10. ## Is CVE-2026-10051 being exploited? There is no known exploitation of CVE-2026-10051 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-10051 and fix it if it is affected. What it is: CVE-2026-10051 is a medium-severity vulnerability in Eclipse Jetty, published on 14 Jul 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-10051 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.36 - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0; fixed in 12.0.36 - org.eclipse.jetty:jetty-server (Maven): affected from 12.1.0; fixed in 12.1.10 - org.eclipse.jetty:jetty-server (Maven): affected from 12.1.0; fixed in 12.1.10 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-10051/ (Markdown: https://insights.sbomify.com/CVE-2026-10051/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10051 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10051 - OSV: https://osv.dev/vulnerability/CVE-2026-10051 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-10051/ Summaries are generated and may contain mistakes; the official description above is the record.