CLEANSTART-2026-SE16040: 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
CVE-2026-18660 affects multiple packages. 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. See references for individual vulnerability details.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
cleanstart/kafkato a version that resolves this vulnerability.Fixed in 4.2.2-r0 - Upgrade
Upgrade
cleanstart/trinoto a version that resolves this vulnerability.Fixed in 482-r3 - Upgrade
Upgrade
cleanstart/trinoto a version that resolves this vulnerability.Fixed in 481-r10
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using the affected Eclipse Jetty jetty-server or jetty-proxy packages are exposed when they rely on host whitelist or blacklist rules. The listed affected software includes cleanstart/trino and cleanstart/kafka.
What does an attacker need to exploit the host-filtering bypass?
An attacker needs to use a host value that differs from an allowed or blocked host only by letter case. Because matching is case-sensitive, that variation can pass through the configured whitelist or blacklist logic.
Are default deployments affected?
The available information only identifies exposure where host whitelist or blacklist controls are used. It does not state whether those controls are enabled or configured by default.
What can be done while patching is unavailable?
Do not rely solely on Jetty host whitelist or blacklist matching for access control where host case variations could matter. Apply equivalent host restrictions in a control that normalizes hostnames or performs case-insensitive matching.