Cilium node based network policies may incorrectly allow workload traffic

Exploitation

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

CVSS

3.4 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2025-30163: 0.21% estimated exploitation activity in the next 30 days; percentile 11.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

24 Mar 2025, 19:36 UTC

Last modified by the source

2 Jul 2026, 20:20 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c6pf-2v8j-96mc

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

# Patch Next advisory brief: CVE-2025-30163

Advisory: Cilium node based network policies may incorrectly allow workload traffic
IDs: CVE-2025-30163, GHSA-c6pf-2v8j-96mc
Record: https://patchnext.com/advisories/cve-2025-30163 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.4)
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.17.2, 1.16.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected >= 1.16.0, < 1.16.8; >= 1.17.0, < 1.17.2; fixed in 1.16.8, 1.17.2

## 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-c6pf-2v8j-96mc (GitHub-reviewed advisory GHSA-c6pf-2v8j-96mc lists affected ranges: Go github.com/cilium/cilium >=1.16.0 =1.17.0 <1.17.2)

Commands are suggestions: review each one before running it.