← Back
CVE-2026-10722
low
CVSS 3.3
Vulnerability in github.com/cilium/ebpf (CVE-2026-10722)
Summary
vulnerability in github.com/cilium/ebpf (CVE-2026-10722). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.22.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-10722** has been found in github.com/cilium/ebpf.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade github.com/cilium/ebpf to **0.22.0** or later.
If unsure, ask your IT team or search "github.com/cilium/ebpf CVE-2026-10722" on the vendor's site.
CVE-2026-10722 (github.com/cilium/ebpf) — CWE-190 / CVSS v3 3.3
Attack vector: local / no user interaction
Patched: `0.22.0` — 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-190) exists in github.com/cilium/ebpf.
📍 Affected scope
github.com/cilium/ebpf — .
🔥 Severity
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.22.0**.
🛡️ 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 'github.com/cilium/ebpf' .` 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 'github.com/cilium/ebpf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/cilium/ebpf` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/cilium/ebpf to 0.22.0ステージング環境で 0.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/cilium/ebpf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.0"}]}]
References
- web https://gist.github.com/thesmartshadow/256bff0f8042c584f993ace89074a815
- web [email protected]
- web https://github.com/cilium/ebpf/commit/533dfc82fd228bfadf42ea7180c39de7d9af47fa
- web https://github.com/cilium/ebpf/issues/2019
- web https://github.com/cilium/ebpf/pull/2021
- web https://vuldb.com/cve/CVE-2026-10722
- web https://vuldb.com/submit/818291
- web https://vuldb.com/vuln/368091
- web https://vuldb.com/vuln/368091/cti
- web https://nvd.nist.gov/vuln/detail/CVE-2026-10722
- web https://github.com/cilium/ebpf
- web https://github.com/advisories/GHSA-xhgw-qwwf-pg32