Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Cilium versions 1.19.0 through 1.19.4 may allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy uses an ipBlock match, but only when Cilium is configured with a custom clusterName instead of the default. An attacker who has a workload in the same namespace as the policy's subject can reach that workload, bypassing the intended restriction. Upgrade to Cilium 1.19.5. As a workaround, the equivalent policy can be written as a CiliumNetworkPolicy using fromCIDR rules, which are not affected.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.4 | Medium | 3.1 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0025, the 16th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-fm8w-2m5w-9j7r
- OSV: GHSA-fm8w-2m5w-9j7r
- github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r
- nvd.nist.gov/vuln/detail/CVE-2026-56743
- github.com/cilium/cilium/pull/46305
- github.com/cilium/cilium/pull/46456
- github.com/cilium/cilium/commit/1c84ae3b58a7cd54f7ee355e6c524c82f620eae8
- github.com/cilium/cilium/commit/bacea640404c0805c23515353dc1681c5bf35171
- github.com/cilium/cilium
- github.com/cilium/cilium/releases/tag/v1.19.5