CVE-2026-6790
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
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 the value provided in the Host header (if present). This mismatch can cause problems such as incorrect URI construction, virtual host selection, reverse proxying, misleading logs, and others.
Risk Assessment
The lack of validation may allow an attacker to manipulate the Host header, leading to redirects to malicious sites, unauthorized access to virtual hosts, or incorrect request routing through reverse proxies, increasing the risk of security breaches and data integrity issues.
Recommendation
It is recommended to immediately update Eclipse Jetty to a version that enforces the match between request authority and Host header as per RFC 9110 and 9112. If an update is not possible, consider implementing temporary firewall or proxy rules to filter mismatched requests.
Other vulnerabilities in Eclipse Jetty
See all- CVE-2015-2080High
The exception handling code in Eclipse Jetty before version 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, known as JetLeak.
- CVE-2026-10050Critical
In Eclipse Jetty, the Digest authentication server-side component uses ISO-8859-1 to encode passwords as bytes, silently replacing characters outside that charset with '?'.
- CVE-2026-8384Medium
In Eclipse Jetty, a vulnerability has been identified involving incorrect path resolution for URIs containing semicolons. A request to a resource like '/public;/../admin/secret.txt' results in Jetty returning an unresolved path '/public/../admin/secret.txt' instead of the expected '/admin/secret.txt'. Jetty itself is not vulnerable because it does not serve files that fail the alias check, but web applications relying on Jetty's path resolution may be confused.
- CVE-2026-10051High
In Eclipse Jetty, the first HTTP/1.1 request with trailers causes the server to retain those trailers for subsequent requests on the same connection. Subsequent requests without trailers report the trailers from the first request, while requests with their own trailers report the union of the first and current request's trailers.
- CVE-2026-2332High
Eclipse Jetty has an HTTP/1.1 request smuggling vulnerability related to chunk extension handling, where the parser terminates chunk extension parsing at \r\n inside quoted strings instead of treating it as an error.
- CVE-2026-5795High
In Eclipse Jetty, the JASPIAuthenticator class sets ThreadLocal variables during authentication but fails to clear them on early return. A subsequent request on the same thread inherits these values, leading to broken access control and privilege escalation.
- CVE-2026-1605High
In Eclipse Jetty versions 12.0.0-12.0.31 and 12.1.0-12.0.5, the GzipHandler class has a memory leak vulnerability. When a compressed HTTP request with Content-Encoding: gzip is processed and the response is not compressed, the JDK Inflater object is not released, causing a resource leak.
Original NVD description (English source)
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.