Network Policies & (Clusterwide) Cilium Network Policies with namespace label selectors may unexpectedly select pods with maliciously crafted labels

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact If a user has Network Policies with namespace selectors selecting labels of namespaces, or (clusterwide) Cilium Network Policies matching on namespace labels, then it is possible for an attacker with Kubernetes pod deploy rights (either directly or indirectly via higher-level APIs such as Deployment, Daemonset etc) to craft additional pod labels such that the pod is selected by another policy that exists rather than the expected policy. Patches The problem has been fixed and is available on versions =1.10.14, =1.11.8, =1.12.1 Workarounds There are no workarounds available. Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Sander Mathijssen for not only highlighting the issue but also proposing a resolution. For more information If you have any questions or comments about this advisory, please reach out on Slack. As usual, if you think you found a related vulnerability, we strongly encourage you…

Published by the source

30 Aug 2022, 20:06 UTC

Last modified by the source

12 Jan 2023, 05:07 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pfhr-pccp-hwmh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pfhr-pccp-hwmh

Advisory: Network Policies & (Clusterwide) Cilium Network Policies with namespace label selectors may unexpectedly select pods with maliciously crafted labels
IDs: GHSA-pfhr-pccp-hwmh
Record: https://patchnext.com/advisories/ghsa-pfhr-pccp-hwmh (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cilium/cilium 1.12.1, 1.11.8, 1.10.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected <= 1.10.13; >= 1.11.0, <= 1.11.7; >= 1.12.0, <= 1.12.0; fixed in 1.10.14, 1.11.8, 1.12.1

## Suggested inspection (read-only)
- Go github.com/cilium/cilium: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cilium/cilium.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pfhr-pccp-hwmh (GitHub-reviewed advisory GHSA-pfhr-pccp-hwmh lists affected ranges: Go github.com/cilium/cilium >=0 =1.11.0 =1.12.0 <=1.12.0)

Commands are suggestions: review each one before running it.