← Back
CVE-2026-10050
critical
CVSS 9.1
Vulnerability in org.eclipse.jetty:jetty-security (CVE-2026-10050)
Summary
vulnerability in org.eclipse.jetty:jetty-security (CVE-2026-10050). Confidential information can be exposed externally. Mitigation: upgrade to `12.1.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-10050** has been found in org.eclipse.jetty:jetty-security.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade org.eclipse.jetty:jetty-security to **12.1.10** or later.
If unsure, ask your IT team or search "org.eclipse.jetty:jetty-security CVE-2026-10050" on the vendor's site.
CVE-2026-10050 (org.eclipse.jetty:jetty-security) — CWE-173 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `12.1.10` — 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-173) exists in org.eclipse.jetty:jetty-security.
📍 Affected scope
org.eclipse.jetty:jetty-security — .
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **12.1.10**.
🛡️ 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-security' .` 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-security' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.eclipse.jetty:jetty-security` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.eclipse.jetty:jetty-security to 12.1.10ステージング環境で 12.1.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.eclipse.jetty:jetty-security
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.10"}]}]
maven
org.eclipse.jetty.ee8:jetty-ee8-security
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.10"}]}]
maven
org.eclipse.jetty.ee9:jetty-ee9-security
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.10"}]}]
References
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- issue [email protected]
- web https://github.com/jetty/jetty.project/issues/15136
- web https://github.com/jetty/jetty.project/pull/15160
- web https://github.com/jetty/jetty.project/pull/15183
- web https://github.com/jetty/jetty.project/commit/4bcdbc7db387ce9e20e2c7571a7250280466221d
- web https://github.com/jetty/jetty.project/commit/d0bb829ccecbf19e3ad3d32f2649b2800f01222d
- web https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.36
- web https://github.com/jetty/jetty.project/releases/tag/jetty-12.1.10
- web https://github.com/advisories/GHSA-2fvj-hgj9-j2gr