Vulnerability in org.eclipse.jetty:jetty-server (CVE-2026-6790)
Summary
Vulnerability in org.eclipse.jetty:jetty-server (CVE-2026-6790). Risk of unauthorized operations or information disclosure. Exploitable via Host header. Mitigation: upgrade to 12.1.9 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-6790 has been found in org.eclipse.jetty:jetty-server.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade org.eclipse.jetty:jetty-server to 12.1.9 or later.
If unsure, ask your IT team or search "org.eclipse.jetty:jetty-server CVE-2026-6790" on the vendor's site.
CVE-2026-6790 (org.eclipse.jetty:jetty-server) — CWE-20 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Host header / HttpURI / Host / MISMATCHED_AUTHORITY
Patched: 12.1.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in org.eclipse.jetty:jetty-server. Attackers reach the vulnerable code path via Host header without authentication.
Check the vendor advisory for the affected versions of org.eclipse.jetty:jetty-server. Attack surface: Host header / HttpURI / Host / MISMATCHED_AUTHORITY.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 12.1.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.eclipse.jetty:jetty-server を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.eclipse.jetty:jetty-server to 12.1.9ステージング環境で 12.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-6790 jetty12
- Ubuntu UBUNTU-CVE-2026-6790 jetty9
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web gitlab.eclipse.org
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com