Advisory record · GHSA-4xp2-w642-7mcx

Cilium vulnerable to bypass of namespace restrictions in CiliumNetworkPolicy

CVSS 6.9 MediumEPSS 0.0048 · 42nd percentile

Published by the GitHub Advisory Database at 27 Sept 2023, 00:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.14.0, <1.14.2 || >=1.13.0, <1.13.7 || <1.12.141.14.2, 1.13.7, 1.12.14
Identifiers
GHSA-4xp2-w642-7mcx · BIT-cilium-2023-41333 · BIT-cilium-operator-2023-41333 · BIT-cilium-proxy-2023-41333 · BIT-hubble-2023-41333 · BIT-hubble-relay-2023-41333 · BIT-hubble-ui-2023-41333 · BIT-hubble-ui-backend-2023-41333 · CVE-2023-41333 · GO-2023-2080
Weakness (CWE)
CWE-306
Published
27 Sept 2023
Updated
10 Sept 2026

Machine-written summary

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

Cilium (github.com/cilium/cilium) versions before 1.12.14, from 1.13.0 before 1.13.7, and from 1.14.0 before 1.14.2 are vulnerable. An attacker who can create or modify CiliumNetworkPolicy objects in one namespace, and has Kubernetes API server access, can use a crafted endpointSelector to bypass namespace restrictions and affect traffic across the cluster. Upgrade to 1.12.14, 1.13.7, 1.14.2, or later; an admission webhook that rejects endpointSelectors using the DoesNotExist operator on the reserved:init label is an available workaround.

Written 2 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
6.9 Medium 3.1 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0048, the 42nd percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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