CVE-2026-18660
validatedZero produced an exploit or a check.GHSA-7wfj-j486-mxrf ↗EUVD-2026-101987 ↗
description
Jetty jetty-server and jetty-proxy host restrictions can treat case variants of the same DNS hostname as different destinations. An attacker able to use a forward proxy or CONNECT handler configured with blacklist-only destination controls may reach a blocked HTTP service or TCP endpoint.
mitigation
Upgrade jetty-server to 12.1.12 or 12.0.39, and jetty-proxy to 11.0.33, 10.0.33, or 9.4.65, as applicable. Until upgraded, use strict allowlists and enforce proxy authentication and network egress controls.
fixed in 12.1.12, 12.0.39, 11.0.33, 10.0.33, 9.4.65
outcome
Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-15 09:38Zghsa: trigger signal, started the run
- 2026-10-15 09:38Zcve.org record for CVE-2026-18660
this entry in the feed
GET /api/v1/feed/CVE-2026-18660
{ "etk_id": "ETK-2026-2023", "cve_id": "CVE-2026-18660", "display_id": "CVE-2026-18660", "ghsa_id": "GHSA-7wfj-j486-mxrf", "euvd_id": "EUVD-2026-101987", "status": "published", "anchor_state": "anchored", "title": "Case-sensitive hostname blacklist bypass in Jetty proxies", "summary": "Jetty jetty-server and jetty-proxy host restrictions can treat case variants of the same DNS hostname as different destinations. An attacker able to use a forward proxy or CONNECT handler configured with blacklist-only destination controls may reach a blocked HTTP service or TCP endpoint.", "mitigation": "Upgrade jetty-server to 12.1.12 or 12.0.39, and jetty-proxy to 11.0.33, 10.0.33, or 9.4.65, as applicable. Until upgraded, use strict allowlists and enforce proxy authentication and network egress controls.", "vendor": "maven", "product": "maven:org.eclipse.jetty:jetty-server", "affected": [ { "affected_notes": [], "affected_ranges": [ ">=12.1.0, <=12.1.11" ], "ecosystem": "maven", "fixed_versions": [ "12.1.12" ], "package_name": "org.eclipse.jetty:jetty-server", "purl": "pkg:maven/org.eclipse.jetty/jetty-server" }, { "affected_notes": [], "affected_ranges": [ ">=12.0.0, <=12.0.38" ], "ecosystem": "maven", "fixed_versions": [ "12.0.39" ], "package_name": "org.eclipse.jetty:jetty-server", "purl": "pkg:maven/org.eclipse.jetty/jetty-server" }, { "affected_notes": [], "affected_ranges": [ ">=11.0.0, <=11.0.32" ], "ecosystem": "maven", "fixed_versions": [ "11.0.33" ], "package_name": "org.eclipse.jetty:jetty-proxy", "purl": "pkg:maven/org.eclipse.jetty/jetty-proxy" }, { "affected_notes": [], "affected_ranges": [ ">=10.0.0, <=10.0.32" ], "ecosystem": "maven", "fixed_versions": [ "10.0.33" ], "package_name": "org.eclipse.jetty:jetty-proxy", "purl": "pkg:maven/org.eclipse.jetty/jetty-proxy" }, { "affected_notes": [], "affected_ranges": [ ">=9.0.0, <=9.4.64" ], "ecosystem": "maven", "fixed_versions": [ "9.4.65" ], "package_name": "org.eclipse.jetty:jetty-proxy", "purl": "pkg:maven/org.eclipse.jetty/jetty-proxy" } ], "cwes": [ 178 ], "cvss_score": 8.2, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N", "epss_score": 0.0032, "epss_percentile": 0.2295, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "mechanism_verified", "exploit": false, "pipeline_minutes": 23.267290733333333, "t0_at": "2026-10-15T09:38:02.125000+00:00", "signals": { "check": { "at": "2026-10-18T23:32:36.381138+00:00", "days": 3.5795631497453706, "is_lower_bound": false, "measured_at": "2026-10-15T09:38:02.125000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-15T09:38:02.125000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-15T09:38:02.125000+00:00", "url": "https://github.com/jetty/jetty.project/security/advisories/GHSA-7wfj-j486-mxrf" } } }
published 2026-10-18 23:09Z
last change 2026-10-21 07:48Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.