Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-6790 medium CVSS 5.3

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.

Summary

Jetty currently accepts HTTP/2 and HTTP/3 requests where the regular
Host header and the pseudo-header :authority
do not match. As a result, the same request can carry two different host identities
through Jetty:

  • logic based on HttpURI / Request.getServerName(request) uses :authority
  • logic based on raw request headers continues to use Host

This creates a host/authority confusion condition that can break
security assumptions in higher layers.

Jetty already performs an explicit authority/Host consistency check on
the HTTP/1.1 path, but equivalent validation is missing on the HTTP/2
and HTTP/3 paths.

Security Impact

This issue is not inherently remote code execution, but it can become
security-relevant in deployments that rely on the request host for
security-sensitive decisions, including:

  • host-based access control
  • virtual host isolation
  • multi-tenant routing by hostname
  • login/logout/callback URL construction
  • reverse proxy and forwarded-header trust chains
  • auditing, cache keys, and absolute URL generation

Potential consequences include:

  • bypass of host-based ACLs
  • virtual host or tenant isolation failures
  • incorrect or attacker-influenced redirect/callback targets
  • inconsistent proxy/downstream interpretation of the original target host
  • misleading logs and audit records

Technical Root Cause

  1. On the HTTP/2 and HTTP/3 metadata builder paths:
  • :authority is parsed separately into authority/URI state
  • Host is p…

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.

❓ What is the problem

A vulnerability (CWE-20) exists in org.eclipse.jetty:jetty-server. Attackers reach the vulnerable code path via Host header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.eclipse.jetty:jetty-server. Attack surface: Host header / HttpURI / Host / MISMATCHED_AUTHORITY.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 12.1.9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.eclipse.jetty:jetty-server を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.eclipse.jetty:jetty-server to 12.1.9

    ステージング環境で 12.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.eclipse.jetty:jetty-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.9"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details