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.
CVE-2026-56743
This medium-severity CVE scores 5.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (6)
Auto-updated Jul 16, 2026Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match · Advisory · cilium/cilium · GitHub
https://github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r1.19.5
Patch available: cilium/cilium v1.19.5
https://github.com/cilium/cilium/releases/tag/v1.19.5[v1.19] fix: Fix wildcard namespace bypass for selectorless ipBlock rules
Fix merged in cilium/cilium PR #46456 on 2026-06-10 — awaiting tagged release
https://github.com/cilium/cilium/pull/46456fix: Fix wildcard namespace bypass for selectorless ipBlock rules
Fix merged in cilium/cilium PR #46305 on 2026-06-09 — awaiting tagged release
https://github.com/cilium/cilium/pull/46305commit bacea640404c (cilium/cilium)
Fix landed in cilium/cilium commit bacea640404c — awaiting tagged release
https://github.com/cilium/cilium/commit/bacea640404c0805c23515353dc1681c5bf35171commit 1c84ae3b58a7 (cilium/cilium)
Fix landed in cilium/cilium commit 1c84ae3b58a7 — awaiting tagged release
https://github.com/cilium/cilium/commit/1c84ae3b58a7cd54f7ee355e6c524c82f620eae8Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 19:45 UTCEG score recompute
- 2026-07-15 19:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(4)
What is CVE-2026-56743?
When was CVE-2026-56743 disclosed?
What is the CVSS score of CVE-2026-56743?
How do I remediate CVE-2026-56743?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56743
Is Your Infrastructure Affected by CVE-2026-56743?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.