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.
References
| Link | Resource |
|---|---|
| https://gitlab.eclipse.org/security/cve-assignment/-/work_items/99 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
14 Jul 2026, 18:35
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:* | |
| First Time |
Eclipse
Eclipse jetty |
|
| References | () https://gitlab.eclipse.org/security/cve-assignment/-/work_items/99 - Vendor Advisory |
14 Jul 2026, 09:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-14 09:16
Updated : 2026-07-14 18:35
NVD link : CVE-2026-6790
Mitre link : CVE-2026-6790
CVE.ORG link : CVE-2026-6790
JSON object : View
Products Affected
eclipse
- jetty
CWE
CWE-20
Improper Input Validation
