CVE-2026-56743: medium-severity vulnerability in cilium
Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.2%
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.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Affected products
cilium · ciliumRelated CVEs — cilium
In the same product, most dangerous first.
CVE-2023-27595MEDIUMCilium eBPF filters may be temporarily removed during agent restartEPSS 0.7%CVE-2023-30851LOWPotential HTTP policy bypass when using header rules in CiliumEPSS 0.7%CVE-2024-28248HIGHCilium intermittent HTTP policy bypassEPSS 0.6%CVE-2024-42486MEDIUMCilium vulnerable to information leakage via incorrect ReferenceGrant update logic in Gateway APIEPSS 0.6%CVE-2023-39347HIGHCilium NetworkPolicy bypass via pod labelsEPSS 0.6%CVE-2023-27594MEDIUMCilium vulnerable to potential network policy bypass when routing IPv6 traffic EPSS 0.6%
References
https://github.com/cilium/cilium/commit/1c84ae3b58a7cd54f7ee355e6c524c82f620eae8https://github.com/cilium/cilium/commit/bacea640404c0805c23515353dc1681c5bf35171https://github.com/cilium/cilium/pull/46305https://github.com/cilium/cilium/pull/46456https://github.com/cilium/cilium/releases/tag/v1.19.5https://github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r