CVE-2026-56743: Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
Impact Standard Kubernetes NetworkPolicy specifications using CIDR-based ipBlock rules without pod or namespace selectors erroneously generate a wildcard namespace allow rule under specific cluster configurations. When Cilium deployment is configured with a specific custom clusterName (rather than the default "any" value), the parser incorrectly instantiates a pod selector on selectorless peer definitions.
Published Sep 3, 2026
Affected packages
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.19.0, < 1.19.5
- Fixed in
- 1.19.5
- Check
go list -m github.com/cilium/cilium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Standard Kubernetes NetworkPolicy specifications using CIDR-based ipBlock rules without pod or namespace selectors erroneously generate a wildcard namespace allow rule under specific cluster configurations.
When Cilium deployment is configured with a specific custom clusterName (rather than the default "any" value), the parser incorrectly instantiates a pod selector on selectorless peer definitions. This leads to Cilium appending an unintended wildcard namespace label selector to the policy's allowed Layer 3 rules, which allows traffic from other workloads in the same namespace as the subject of the policy.
Example policy affected by this issue:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: test-server
namespace: default
spec:
podSelector:
matchLabels:
app: test-server
policyTypes:
- Ingress
ingress:
- from:
- ipBlock:
cidr: 192.0.2.3In affected versions, this policy erroneously allows the test-server Pod in the default namespace to receive any traffic from other workloads running in the default namespace.
Patches
This issue has been patched in:
- Cilium v1.19.5
Releases below v1.19.0 are not affected.
This issue affects:
- Cilium v1.19 between v1.19.0 and v1.19.4 inclusive
Workarounds
Developers can create the equivalent policy using CiliumNetworkPolicy fromCIDR expressions. CiliumNetworkPolicy and CiliumClusterwideNetworkPolicy are not affected by this issue.
Acknowledgements
Special thanks to @TheBeeZee for reporting this issue and preparing the fix, and to @fristonio and @odinuge for their assistance in reviewing the solution.
For more information
If a vulnerability affecting Cilium appears to have been found, the Cilium security team strongly encourages reporting it to the security mailing list at [email protected]. This is a private mailing list for the Cilium security team, and the report will be treated as top priority.
References
- https://github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r
- https://nvd.nist.gov/vuln/detail/CVE-2026-56743
- https://github.com/cilium/cilium/pull/46305
- https://github.com/cilium/cilium/pull/46456
- https://github.com/cilium/cilium/commit/1c84ae3b58a7cd54f7ee355e6c524c82f620eae8
- https://github.com/cilium/cilium/commit/bacea640404c0805c23515353dc1681c5bf35171
- https://github.com/cilium/cilium/releases/tag/v1.19.5
- https://github.com/advisories/GHSA-fm8w-2m5w-9j7r
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-56742
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
medium5.9Sep 24, 2026CVE-2026-49445
Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access
critical9.2Jul 6, 2026CVE-2026-53935
CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
medium6.9Jul 6, 2026CVE-2026-41520
Cillium exposes sensitive information included in the cilium-bugtool debug archive
high7.9Apr 25, 2026CVE-2026-33726
Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic
medium5.4Mar 26, 2026CVE-2026-26963
Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled
medium6.1Feb 19, 2026
