← Back
CVE-2026-8384
medium
CVSS 5.3
Vulnerability in org.eclipse.jetty:jetty-util (CVE-2026-8384)
Summary
vulnerability in org.eclipse.jetty:jetty-util (CVE-2026-8384). Risk of unauthorized operations or information disclosure. Exploitable via `GET /admin/secret`. Mitigation: upgrade to `12.1.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-8384** has been found in org.eclipse.jetty:jetty-util.
Attackers can target a specific entry point like `GET /admin/secret` 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-util to **12.1.9** or later.
If unsure, ask your IT team or search "org.eclipse.jetty:jetty-util CVE-2026-8384" on the vendor's site.
CVE-2026-8384 (org.eclipse.jetty:jetty-util) — CWE-647 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /admin/secret / GET /public / `SecurityHandler.PathMapped` / `Authorization`
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-647) exists in org.eclipse.jetty:jetty-util. Attackers reach the vulnerable code path via `GET /admin/secret` without authentication.
📍 Affected scope
org.eclipse.jetty:jetty-util — . Attack surface: GET /admin/secret / GET /public / `SecurityHandler.PathMapped` / `Authorization`.
🔥 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 `GET /admin/secret` requests with malformed payloads or SQL meta-characters. Run `grep -r 'org.eclipse.jetty:jetty-util' .` 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-util' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.eclipse.jetty:jetty-util` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /admin/secret' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /admin/secret` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade org.eclipse.jetty:jetty-util to 12.1.9ステージング環境で 12.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /admin/secret on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.eclipse.jetty:jetty-util
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.9"}]}]
References
- web https://gitlab.eclipse.org/security/cve-assignment/-/work_items/108
- web https://github.com/jetty/jetty.project/security/advisories/GHSA-w7x5-g22v-xqhr
- web https://nvd.nist.gov/vuln/detail/CVE-2026-8384
- web https://github.com/jetty/jetty.project/pull/14969
- web https://github.com/jetty/jetty.project/pull/14973
- web https://github.com/jetty/jetty.project/commit/82969c77f6da46e27008b10b3c14840cd31db084
- web https://github.com/jetty/jetty.project/commit/ade27ce93a37c33278720250d85c48601230ae3f
- 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-w7x5-g22v-xqhr