Ad · Leaderboard 728×90

CVE-2026-18660

8.8High

Published 15 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash

8.8High
Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None
Impact
High impact on confidentiality
Weakness
CWE-178, CWE-918

Impact

Remote attackers can bypass host access controls and potentially trigger SSRF attacks against internal hosts without authentication. They only need network access to send requests with mixed-case host headers.

Root cause

Eclipse Jetty's host whitelist and blacklist checks in jetty-server and jetty-proxy perform case-sensitive string comparisons instead of case-insensitive domain matching.

Affected systems

Versions not listed — check the vendor advisory.

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade jetty-server and jetty-proxy to patched releases specified in GHSA-7wfj-j486-mxrf once available. As an interim workaround, normalize Host headers to lowercase via an upstream reverse proxy or WAF before traffic reaches Jetty.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

In Eclipse Jetty, across various versions of `jetty-server`, and `jetty-proxy`, the host whitelist/blacklist is case-sensitive, and would allow hosts through that only differ by case.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-18660

Ad · Sticky 320×50 / 728×90