Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic

TRUNG BÌNH 4.3CVE-2026-33726 · BIT-cilium-2026-33726 · BIT-cilium-operator-2026-33726 · Công bố 27/03/2026 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2026-33726 là lỗ hổng mức TRUNG BÌNH (CVSS 4.3) ảnh hưởng github.com/cilium/cilium, cilium (cilium).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.26%, cao hơn 17.3% các lỗ hổng khác.
Cách xử lý: cập nhật lên 1.18.8, 1.19.2, 1.17.14 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/cilium/cilium Go	`≥ 1.18.0, < 1.18.8≥ 1.19.0, < 1.19.2< 1.17.14`	`1.18.81.19.21.17.14`
cilium cilium	`≥ 1.18.0, < 1.18.8≥ 1.19.0, < 1.19.2< 1.17.14`	`1.18.81.19.21.17.14`

Mô tả

Impact

Ingress Network Policies are not enforced for traffic from pods to L7 Services (Envoy, GAMMA) with a local backend on the same node, when Per-Endpoint Routing is enabled and BPF Host Routing is disabled.

Per-Endpoint Routing is disabled by default, but is automatically enabled in deployments using cloud IPAM, including Cilium ENI on EKS (eni.enabled), AlibabaCloud ENI (alibabacloud.enabled), Azure IPAM (azure.enabled, but not AKS BYOCNI), and some GKE deployments (gke.enabled; managed offerings such as GKE Dataplane V2 may use different defaults). It is typically not enabled in tunneled deployments, and chaining deployments are not affected. In practice, Amazon EKS with Cilium ENI mode is likely the most common affected environment.

Patches

This issue was fixed by #44693.

This issue affects:

Cilium v1.19 between v1.19.0 and v1.19.1 inclusive
Cilium v1.18 between v1.18.0 and v1.18.7 inclusive
All versions of Cilium prior to v1.17.13

This issue is fixed in:

Cilium v1.19.2
Cilium v1.18.8
Cilium v1.17.14

Workarounds

Disclaimer: There is currently no officially verified or comprehensive workaround for this issue. The only option would be to disable per-endpoint routes, but this will likely cause disruptions to ongoing connections, and potential conflicts if running in cloud providers.

Acknowledgements

The Cilium community has worked together with members of the Northflank and Isovalent teams to prepare these mitigations. Cilium thanks @sudeephb and @Champ-Goblem for reporting the issue and to @smagnani96 and @julianwiedmann for helping with the resolution.

For more information

Anyone who believes a vulnerability affecting Cilium has been found is strongly encouraged to report it to the security mailing list at [email protected]. This is a private mailing list for the Cilium security team, and any such report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.

Mô tả của NVD

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.14, 1.18.8, and 1.19.2, Ingress Network Policies are not enforced for traffic from pods to L7 Services (Envoy, GAMMA) with a local backend on the same node, when Per-Endpoint Routing is enabled and BPF Host Routing is disabled. Per-Endpoint Routing is disabled by default, but is automatically enabled in deployments using cloud IPAM, including Cilium ENI on EKS (`eni.enabled`), AlibabaCloud ENI (`alibabacloud.enabled`), Azure IPAM (`azure.enabled`, but not AKS BYOCNI), and some GKE deployments (`gke.enabled`; managed offerings such as GKE Dataplane V2 may use different defaults). It is typically not enabled in tunneled deployments, and chaining deployments are not affected. In practice, Amazon EKS with Cilium ENI mode is likely the most common affected environment. Versions 1.17.14, 1.18.8, and 1.19.2 contain a patch. There is currently no officially verified or comprehensive workaround for this issue. The only option would be to disable per-endpoint routes, but this will likely cause disruptions to ongoing connections, and potential conflicts if running in cloud providers.