Advisory record · GHSA-hxv8-4j4r-cqgv

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

CVSS 5.4 MediumEPSS 0.0024 · 15th percentile

Published by the GitHub Advisory Database at 26 Mar 2026, 16:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo<1.17.14 || >=1.18.0, <1.18.8 || >=1.19.0, <1.19.21.17.14, 1.18.8, 1.19.2
Identifiers
GHSA-hxv8-4j4r-cqgv · BIT-cilium-2026-33726 · BIT-cilium-operator-2026-33726 · BIT-hubble-relay-2026-33726 · CVE-2026-33726 · GO-2026-4856
Weakness (CWE)
CWE-284 · CWE-863
Published
26 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Cilium (Go module github.com/cilium/cilium) versions before 1.17.14, from 1.18.0 up to 1.18.8, and from 1.19.0 up to 1.19.2 are affected. Ingress Network Policies are not enforced for pod traffic to L7 Services with a local backend on the same node when Per-Endpoint Routing is enabled and BPF Host Routing is disabled, so a pod can reach such a backend despite the policy. Upgrade to 1.17.14, 1.18.8, 1.19.2 or later. The source gives no workaround beyond disabling per-endpoint routes, which may disrupt connections.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0024, the 15th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.