NetSight
medium5.3

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 and port) matches what provided in the Host…

Impact

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 packages

EcosystemPackageAffectedFixed in
mavenorg.eclipse.jetty:jetty-server>= 9.4.0.v20161208, <= 9.4.58.v20250814none recorded

Affected products

VendorProductAffected versions
EclipseJetty
from 9.4.0 before 9.4.61
from 10.0.0 before 10.0.29
from 11.0.0 before 11.0.29
from 12.0.0 before 12.0.35
from 12.1.0 before 12.1.9

Weakness classification

References