CVE-2026-6790

Published Jul 14, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7p3p-8qv8-m2vh Eclipse Jetty: HTTP Authority/Host mismatch
History
Type Values Removed Values Added
Title Missing Authority and Host Header Validation in Eclipse Jetty
Type Values Removed Values Added
Title Missing Authority and Host Header Validation in Eclipse Jetty
Type Values Removed Values Added
Title Jetty Host Header Authority Mismatch Vulnerability
Type Values Removed Values Added
Title Jetty Host Header Authority Mismatch Vulnerability
Type Values Removed Values Added
Title Jetty Host Header and Authority Validation Missing
Type Values Removed Values Added
Title Jetty Host Header and Authority Validation Missing
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Eclipse
Eclipse jetty
Vendors & Products Eclipse
Eclipse jetty
Type Values Removed Values Added
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.
Weaknesses CWE-20
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Jul 14, 2026, 12:20 PM
Reserved
Apr 21, 2026, 1:47 PM
Status
Analyzed
Published
Jul 14, 2026, 9:16 AM
Modified
Oct 24, 2026, 9:10 PM