Advisory record · GHSA-fm8w-2m5w-9j7r

Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match

CVSS 5.4 MediumEPSS 0.0025 · 16th percentile

Published by the GitHub Advisory Database at 3 Sept 2026, 17:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.19.0, <1.19.51.19.5
Identifiers
GHSA-fm8w-2m5w-9j7r · BIT-cilium-2026-56743 · BIT-cilium-operator-2026-56743 · BIT-hubble-relay-2026-56743 · CVE-2026-56743 · GO-2026-6367
Weakness (CWE)
CWE-863
Published
3 Sept 2026
Updated
10 Sept 2026

Machine-written summary

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

Cilium versions 1.19.0 through 1.19.4 may allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy uses an ipBlock match, but only when Cilium is configured with a custom clusterName instead of the default. An attacker who has a workload in the same namespace as the policy's subject can reach that workload, bypassing the intended restriction. Upgrade to Cilium 1.19.5. As a workaround, the equivalent policy can be written as a CiliumNetworkPolicy using fromCIDR rules, which are not affected.

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.0025, the 16th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 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.