← Back
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.
AI summary snake-internal / snake-material-v2
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
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. Run `grep -r 'org.eclipse.jetty:jetty-server' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.eclipse.jetty:jetty-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.eclipse.jetty:jetty-server` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.eclipse.jetty:jetty-server to 12.1.9ステージング環境で 12.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.eclipse.jetty:jetty-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.9"}]}]
References
- web https://gitlab.eclipse.org/security/cve-assignment/-/work_items/99
- web https://github.com/jetty/jetty.project/security/advisories/GHSA-7p3p-8qv8-m2vh
- web https://nvd.nist.gov/vuln/detail/CVE-2026-6790
- web https://github.com/jetty/jetty.project/issues/14870
- web https://github.com/jetty/jetty.project/pull/14871
- web https://github.com/jetty/jetty.project/pull/14897
- web https://github.com/jetty/jetty.project/pull/14970
- web https://github.com/jetty/jetty.project/commit/3e5a4daec196859b8886b6f67b1157dab47cdb6f
- web https://github.com/jetty/jetty.project/commit/67ba9e6b39661810123680d9c894e99a7940c73d
- web https://github.com/jetty/jetty.project/commit/cbca3076f7c914a232e7a8b22fa95fbf7e67a6cc
- web https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.35
- web https://github.com/jetty/jetty.project/releases/tag/jetty-12.1.9
- web https://github.com/advisories/GHSA-7p3p-8qv8-m2vh