---
id: CVE-2025-30162
aliases:
  - GHSA-24qp-4xx8-3jvj
  - BIT-cilium-2025-30162
  - BIT-cilium-operator-2025-30162
  - BIT-hubble-relay-2025-30162
  - GO-2025-3560
title: >-
  Cilium East-west traffic not subject to egress policy enforcement for requests
  via Gateway API load balancers
summary: >-
  Cilium East-west traffic not subject to egress policy enforcement for requests
  via Gateway API load balancers
severity: low
cvss: 3.2
cvssVector: 'CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N'
vendor: cilium
product: github.com/cilium/cilium
ecosystem: go
affected:
  - 'github.com/cilium/cilium >= 1.16.0, < 1.16.8'
  - 'github.com/cilium/cilium >= 1.17.0, < 1.17.2'
  - 'github.com/cilium/cilium >= 1.15.0, < 1.15.15'
patched:
  - github.com/cilium/cilium 1.16.8
  - github.com/cilium/cilium 1.17.2
  - github.com/cilium/cilium 1.15.15
published: '2025-03-24'
updated: '2026-09-10'
sourceUpdated: '2026-09-10T03:50:06.165871995Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-24qp-4xx8-3jvj'
references:
  - url: 'https://github.com/cilium/cilium/security/advisories/GHSA-24qp-4xx8-3jvj'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2025-30162'
  - url: 'https://github.com/cilium/proxy/pull/1172'
  - url: 'https://docs.cilium.io/en/stable/network/lb-ipam'
  - url: 'https://github.com/cilium/cilium'
tags:
  - osv
  - go
epss: 0.0022
epssPercentile: 0.11062
ingestedAt: '2026-09-12T03:13:01.744Z'
---

## Overview

### Impact

For Cilium users who:
- Use Gateway API for Ingress for some services **AND**
- Use [LB-IPAM](https://docs.cilium.io/en/stable/network/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.

### Patches

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

This issue affects:

- Cilium v1.15 between v1.15.0 and v1.15.14 inclusive
- 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.15.15
- Cilium v1.16.8
- Cilium v1.17.2

### Workarounds

A Clusterwide Cilium Network Policy can be used to work around this issue for users who are unable to upgrade. An outline of such a policy is provided below:

```
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: "workaround"
spec:
  endpointSelector:
    matchExpressions:
    - key: reserved:ingress
      operator: Exists
  ingress:
  - fromEntities:
    - world
```

- The policy opens up connectivity from all locations outside the cluster into the Cilium Ingress Gateway.
- The policy establishes a default deny for all other traffic towards the Cilium Ingress Gateway, including all in-cluster sources.
- It is possible to tailor the policy to more narrowly allow inbound traffic while creating a default deny posture for traffic between namespaces. Users should edit the policy to bring it in line with the security requirements particular to their environments.

### Acknowledgements

The Cilium community has worked together with members of the Isovalent team to prepare these mitigations. Special thanks to @jrajahalme for the fix.

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

## Affected packages

- `github.com/cilium/cilium >= 1.16.0, < 1.16.8`
- `github.com/cilium/cilium >= 1.17.0, < 1.17.2`
- `github.com/cilium/cilium >= 1.15.0, < 1.15.15`

## Remediation

Upgrade to a patched release:

- `github.com/cilium/cilium 1.16.8`
- `github.com/cilium/cilium 1.17.2`
- `github.com/cilium/cilium 1.15.15`