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

Published Nov 20, 2026
·
Updated

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

3 affected componentsFixes available
cleanstart/kafka<4.2.2-r0
4.2.2-r0
cleanstart/trino<482-r3
482-r3
cleanstart/trino<481-r10
481-r10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade cleanstart/kafka to a version that resolves this vulnerability.

    Fixed in 4.2.2-r0
  2. Upgrade

    Upgrade cleanstart/trino to a version that resolves this vulnerability.

    Fixed in 482-r3
  3. Upgrade

    Upgrade cleanstart/trino to a version that resolves this vulnerability.

    Fixed in 481-r10

Event History

Nov 20, 2026
Advisory Published
via OSV·12:39 AM
Data Sourced
via OSV·12:39 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203