Untriaged
Permalink
CVE-2026-56743
5.4 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Adjacent (A)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Changed (C)
- Confidentiality (C): Low (L)
- Integrity (I): Low (L)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Adjacent (A)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): Low (L)
- Modified Scope (MS): Changed (C)
- Modified Integrity (MI): Low (L)
- Modified Availability (MA): None (N)
Activity log
- Created suggestion
Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
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.
References
-
https://github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r x_refsource_CONFIRM
-
https://github.com/cilium/cilium/pull/46305 x_refsource_MISC
-
https://github.com/cilium/cilium/pull/46456 x_refsource_MISC
-
https://github.com/cilium/cilium/releases/tag/v1.19.5 x_refsource_MISC
Affected products
cilium
- ==>= 1.19.0, < 1.19.5
Package maintainers
-
@ryan4yin Ryan Yin <xiaoyin_c@qq.com>
-
@akshatagarwl Akshat Agarwal <humancalico@disroot.org>
-
@qjoly Quentin JOLY <github@une-pause-cafe.fr>