Skip to content
fr Sign in
5.3 Medium

CVE-2026-6790 In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host…

Description

In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.

Affected products and versions

Product Affected versions Fixed in
Eclipse Jetty 12.1 12.1.0 → 12.1.8 No fix stated
Eclipse Jetty 12.0 12.0.0 → 12.0.34 No fix stated
Eclipse Jetty 11.0 11.0.0 → 11.0.28 No fix stated
Eclipse Jetty 10.0 10.0.0 → 10.0.28 No fix stated
Eclipse Jetty 9.4 9.4.0 → 9.4.60 No fix stated

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Eclipse Jetty

The 16 CVEs of Eclipse Jetty →
CVE-2026-18661 In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec… 8.8 High CVE-2026-77711 When Jetty's `HttpClient` make a request to a server through a forward proxy, the server may reply with a 407 (Proxy… 8.2 High CVE-2026-76184 In Eclipse Jetty, HttpClient may receive a redirect of the form: ``` /secure/../evil ``` If an attacker is able to… 8.2 High CVE-2026-76182 In Eclipse Jetty, `TryPathsHandler` and `TryFilesFilter` can be configured to forward requests to template URIs such… 6.9 Medium
Track this CVE