Description
Cilium is a networking, observability, and security solution. From 1.19.0 to 1.19.4, standard Kubernetes NetworkPolicy specifications using CIDR-based ipBlock rules without pod or namespace selectors erroneously generate a wildcard namespace allow rule when Cilium is configured with a custom clusterName rather than the default any value. The parser incorrectly instantiates a pod selector on selectorless peer definitions, allowing traffic from other workloads in the same namespace as the subject of the policy. This issue is fixed in version 1.19.5.
Affected products
cilium: cilium
References6
- github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r Vendor Advisory
- github.com/cilium/cilium/commit/1c84ae3b58a7cd54f7ee355e6c524c8… Patch
- github.com/cilium/cilium/commit/bacea640404c0805c23515353dc1681… Patch
- github.com/cilium/cilium/pull/46305 Patch
- github.com/cilium/cilium/pull/46456 Patch
- github.com/cilium/cilium/releases/tag/v1.19.5 Release Notes
Metrics
- CVSS 3.1
-
5.4
MEDIUM
Score source: CNA
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 16 · as of 15 November 2026
- CWE
- CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.