LowGHSA-c6pf-2v8j-96mcBIT-cilium-2025-30163BIT-cilium-operator-2025-30163BIT-hubble-relay-2025-30163CVE-2025-30163

Cilium node based network policies may incorrectly allow workload traffic

Published 24 Mar 2025 · Updated 2 Jul 2026

Is your project on an affected github.com/cilium/cilium?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.16.0 <1.16.8
Fixed in
1.16.8
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.16.8
Affected
>=1.17.0 <1.17.2
Fixed in
1.17.2
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.17.2

Details

Impact

Node based network policies (fromNodes and toNodes) will incorrectly permit traffic to/from non-node endpoints that share the labels specified in fromNodes and toNodes sections of network policies. Node based network policy is disabled by default in Cilium.

Patches

This issue was fixed by https://github.com/cilium/cilium/pull/36657.

This issue affects:

  • Cilium v1.16 between v1.16.0 and v1.16.7 inclusive
  • Cilium v1.17 between v1.17.0 and v1.17.1 inclusive

This issue is fixed in:

  • Cilium v1.16.8
  • Cilium v1.17.2

Workarounds

Users can work around this issue by ensuring that the labels used in fromNodes and toNodes fields are used exclusively by nodes and not by other endpoints.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @oblazek for reporting and fixing this issue.

For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.

Is GHSA-c6pf-2v8j-96mc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cilium/cilium, and gives you the command that fixes it.

More advisories for github.com/cilium/cilium

  • LowCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces in github.com/cilium/cilium · 1 Oct 2026
  • MediumCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces · 24 Sept 2026
  • LowCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match in github.com/cilium/cilium · 10 Sept 2026
  • MediumCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match · 3 Sept 2026
  • LowCVE-2026-49445Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access in github.com/cilium/cilium · 7 Jul 2026
  • LowCVE-2026-53935CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation in github.com/cilium/cilium · 7 Jul 2026
All 75 advisories for github.com/cilium/cilium

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.