Skip to main content
← All vulnerabilities
CVE-2026-6790GHSA-7P3P-8QV8-M2VH

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 p

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 12.0.35, 12.1.9
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

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

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  3. Record last updated

Affected versions

  • Eclipse Foundation Eclipse Jetty

    From 9.4.0 · through 9.4.60; From 10.0.0 · through 10.0.28; From 11.0.0 · through 11.0.28; From 12.0.0 · through 12.0.34; From 12.1.0 · through 12.1.8

  • org.eclipse.jetty:jetty-serverMaven

    From 9.4.0.v20161208 · through 9.4.58.v20250814

  • org.eclipse.jetty:jetty-serverMaven

    From 10.0.0 · through 10.0.26

  • org.eclipse.jetty:jetty-serverMaven

    From 11.0.0 · through 11.0.26

  • org.eclipse.jetty:jetty-serverMaven

    From 12.0.0 · fixed in 12.0.35

  • org.eclipse.jetty:jetty-serverMaven

    From 12.1.0 · fixed in 12.1.9

References 1

gitlab.eclipse.org