CVE-2025-30162
For Cilium users who use Gateway API for Ingress for some services and use LB-IPAM or BGP for LB Service implementation and use network policies to block egress traffic from workloads in a namespace to workloads in other namespaces, egress traffic from…
Does this matter?
Lower severity and a low EPSS score (0.22%). Track it; it rarely justifies an emergency change on its own.
Description
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. For Cilium users who use Gateway API for Ingress for some services and use LB-IPAM or BGP for LB Service implementation and use network policies to block egress traffic from workloads in a namespace to workloads in other namespaces, egress traffic from workloads covered by such network policies to LoadBalancers configured by `Gateway` resources will incorrectly be allowed. LoadBalancer resources not deployed via a Gateway API configuration are not affected by this issue. This issue affects: Cilium v1.15 between v1.15.0 and v1.15.14 inclusive, v1.16 between v1.16.0 and v1.16.7 inclusive, and v1.17 between v1.17.0 and v1.17.1 inclusive. This issue is fixed in Cilium v1.15.15, v1.16.8, and v1.17.2. A Clusterwide Cilium Network Policy can be used to work around this issue for users who are unable to upgrade.
- CVSS 3.1
- 4.3 MEDIUMCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- EPSS
- 0.22% probability · 13th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-863
- Affected
- cilium/cilium
- Source
- security-advisories@github.com
References
- https://docs.cilium.io/en/stable/network/lb-ipamProduct
- https://github.com/cilium/cilium/security/advisories/GHSA-24qp-4xx8-3jvjMitigation, Patch, Third Party Advisory
- https://github.com/cilium/proxy/pull/1172Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.