Vulnerability in github.com/cilium/cilium (CVE-2026-49445)
Summary
Vulnerability in github.com/cilium/cilium (CVE-2026-49445). Confidential information can be exposed externally. Mitigation: upgrade to 1.17.14, 1.18.8, 1.19.2 or later.
Original description
The description as published by the source.
Cilium is a networking, observability, and security solution. Prior to 1.17.14, 1.18.8, and 1.19.2, when Cilium L7 functionality is enabled, the embedded or standalone Envoy instance creates a world-accessible admin.sock on cluster nodes, allowing a local attacker to access Envoy admin endpoints, expose TLS secrets, disrupt cluster traffic, or terminate Envoy. This issue is fixed in versions 1.17.14, 1.18.8, and 1.19.2.
Source: GitHub Security Advisories (Global) 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-49445 has been found in github.com/cilium/cilium.
Confidential information can be exposed externally. CVSS score: 9.2/10.
What to do: upgrade github.com/cilium/cilium to 1.17.14, 1.18.8, 1.19.2 or later.
If unsure, ask your IT team or search "github.com/cilium/cilium CVE-2026-49445" on the vendor's site.
CVE-2026-49445 (github.com/cilium/cilium) — CWE-862 / CVSS v3 9.2
Attack vector: local / unauthenticated / no user interaction
Patched: 1.17.14, 1.18.8, 1.19.2 — 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.
A vulnerability (CWE-862) exists in github.com/cilium/cilium.
Check the vendor advisory for the affected versions of github.com/cilium/cilium.
Severity: Critical (CVSS 9.2/10). Confidential information can be exposed externally.
Update to 1.17.14, 1.18.8, 1.19.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/cilium/cilium' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/cilium/cilium' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/cilium/ciliumを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/cilium/cilium to 1.17.14, 1.18.8, 1.19.2ステージング環境で 1.17.14, 1.18.8, 1.19.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov