cilium · Cilium · published 2026-07-15
CVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-56743 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 16% of all CVEs. This Cilium vulnerability: CVSS 5.4 (v3.1). Fixed upstream in Cilium 1.19.5, 1.18.11, 1.17.17. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Cilium 1.19.5, 1.18.11, 1.17.17.
Patch events
OrchestrationCilium
Cilium security releases: 1.19.5, 1.18.11, 1.17.17
Upgrade to
1.19.51.18.111.17.17Why: Vendor security release for server software (most severe: CVE-2026-56742).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (16th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.4 (v3.1)CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- cilium cilium
>= 1.19.0, < 1.19.5(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.