Vulnerability in github.com/cilium/cilium (CVE-2026-56742)
Summary
Vulnerability in github.com/cilium/cilium (CVE-2026-56742). Risk of unauthorized operations or information disclosure. Exploitable via HTTPRoute. Mitigation: upgrade to 1.19.5 or later.
Original description
The description as published by the source.
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces in github.com/cilium/cilium
Source: NIST National Vulnerability Database 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-56742 has been found in github.com/cilium/cilium.
Attackers can target a specific entry point like HTTPRoute over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: upgrade github.com/cilium/cilium to 1.19.5 or later.
If unsure, ask your IT team or search "github.com/cilium/cilium CVE-2026-56742" on the vendor's site.
CVE-2026-56742 (github.com/cilium/cilium) — CWE-862 / CVSS v3 5.9
Attack vector: adjacent-network / no user interaction
Attack surface: HTTPRoute
Patched: 1.19.5 — apply immediately
Workaround: There is no workaround to this issue.
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. Attackers reach the vulnerable code path via HTTPRoute.
Check the vendor advisory for the affected versions of github.com/cilium/cilium. Attack surface: HTTPRoute.
Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.
Update to 1.19.5.
Workaround: There is no workaround to this issue.
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 temporary workaround mitigate
There is no workaround to this issue.パッチが適用されるまでの応急処置として、There is no workaround to this issue. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/cilium/cilium to 1.19.5ステージング環境で 1.19.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com