Network policy bypass via selectorless ipBlock parsing
Published Jul 15, 2026 · Updated Jul 15, 2026
Incorrect authorization in Cilium 1.19.0 through 1.19.4 allows remote authenticated users to bypass ingress policy via same-namespace traffic. The pkg/k8s NetworkPolicy parser instantiates a pod selector for an ipBlock-only peer and appends an unintended wildcard namespace selector. Exploitation requires a custom clusterName and a standard NetworkPolicy ipBlock peer without pod or namespace selectors, exposing protected pods to other workloads in their namespace.
Summary
What happened
Incorrect authorization in Cilium 1.19.0 through 1.19.4 allows remote authenticated users to bypass ingress policy via same-namespace traffic. The pkg/k8s NetworkPolicy parser instantiates a pod selector for an ipBlock-only peer and appends an unintended wildcard namespace selector. Exploitation requires a custom clusterName and a standard NetworkPolicy ipBlock peer without pod or namespace selectors, exposing protected pods to other workloads in their namespace.
The record
- CVE
- CVE-2026-56743
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Cilium
- Product
- Cilium
- Classifications
- CWE-863, T1210
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.19.0, < 1.19.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo