← Übersicht Cilium

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

CVE-2026-33726 · BIT-cilium-2026-33726 · BIT-cilium-operator-2026-33726 · BIT-hubble-relay-2026-33726 · DHI-qyzy-6zym-zb6w-nkj3 · GHSA-hxv8-4j4r-cqgv · GO-2026-4856

Mittel · CVSS 5.4 Nachbarnetz Fix verfügbar

Veröffentlicht
26.03.2026 17:48
Zuletzt geändert
18.11.2026
EPSS (30 Tage)
0.2 %
CVSS-Vektor
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Betroffene Pakete im beobachteten Stack

CVEcilium/ciliumkein Fix bekanntCVE-2026-33726
Gogithub.com/cilium/cilium1.17.14GHSA-hxv8-4j4r-cqgv
Gogithub.com/cilium/cilium1.18.0 → 1.18.8GHSA-hxv8-4j4r-cqgv
Gogithub.com/cilium/cilium1.19.0 → 1.19.2GHSA-hxv8-4j4r-cqgv
Gogithub.com/cilium/cilium1.17.14, 1.18.0 → 1.18.8, 1.19.0 → 1.19.2GO-2026-4856
NVDcilium:cilium1.17.14, 1.18.0 → 1.18.8, 1.19.0 → 1.19.2CVE-2026-33726
Weitere betroffene Pakete (11)
Bitnamicilium1.17.14, 1.18.0 → 1.18.8, 1.19.0 → 1.19.2BIT-cilium-2026-33726
Bitnamicilium-operator1.17.14, 1.18.0 → 1.18.8, 1.19.0 → 1.19.2BIT-cilium-operator-2026-33726
Bitnamihubble-relay1.17.14, 1.18.0 → 1.18.8, 1.19.0 → 1.19.2BIT-hubble-relay-2026-33726
Docker Hardened Images:Alpine:3.23cilium-operatorkein Fix bekanntDHI-qyzy-6zym-zb6w-nkj3
Docker Hardened Images:Alpine:3.23cilium-operator-devkein Fix bekanntDHI-qyzy-6zym-zb6w-nkj3
Docker Hardened Images:Alpine:3.23cilium-operator-fipskein Fix bekanntDHI-qyzy-6zym-zb6w-nkj3
Docker Hardened Images:Alpine:3.23cilium-operator-fips-devkein Fix bekanntDHI-qyzy-6zym-zb6w-nkj3
Docker Hardened Images:Alpine:3.23hubble-ui-backendkein Fix bekanntDHI-qyzy-6zym-zb6w-nkj3
Docker Hardened Images:Alpine:3.23hubble-ui-backend-fipskein Fix bekanntDHI-qyzy-6zym-zb6w-nkj3
openSUSE:Leap 15.6govulncheck-vulndb0.0.20260326T203309-150000.1.155.2SUSE-SU-2026:1135-1
openSUSE:Leap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Nachbarnetz) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.