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 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.

Published: 2026-07-14 Last update: 2026-07-14 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-6790 is rated Low Risk (24.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.20%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-6790

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-14 — 0.20% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-6790

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2026-6790

OS Trackers for CVE-2026-6790

vendor priority summary link
debian not yet assigned CVE-2026-6790 not yet assigned priority: Debian including 2 source packages (jetty12, jetty9), 8 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 8. https://security-tracker.debian.org/tracker/CVE-2026-6790
ubuntu medium CVE-2026-6790 medium priority: Ubuntu including 2 source packages (jetty12, jetty9), 10 status rows across 6 suites (bionic, focal, jammy, noble, resolute, upstream): needs-triage 8, DNE 2. https://ubuntu.com/security/CVE-2026-6790

Affected software / configurations for CVE-2026-6790

Vendor Product Version Raw CPE
eclipse jetty >= 9.4.0, < 9.4.61 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 10.0.0, < 10.0.29 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 11.0.0, < 11.0.29 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 12.0.0, < 12.0.35 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 12.1.0, < 12.1.9 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*

References for CVE-2026-6790

cvelogic Threat Intelligence