# CVE-2025-30162: East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers > Attackers can bypass egress network policies for traffic routed through Gateway API load balancers in specific Cilium configurations. - **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Mar 2025 - **Updated:** 24 Mar 2025 - **Also known as:** BIT-cilium-2025-30162, BIT-cilium-operator-2025-30162, BIT-hubble-relay-2025-30162, GHSA-24qp-4xx8-3jvj, GO-2025-3560, MINI-27jf-56f7-w482, MINI-5r94-cwv7-wvh4, MINI-p8wq-3f9h-6f2m, MINI-pwph-vrqh-xpmq ## What is CVE-2025-30162? CVE-2025-30162 is a low-severity missing authorization vulnerability in cilium, published on 24 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2025-30162? 10 open source packages ship an affected version, including github.com/cilium/cilium, cilium and cilium-operator. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/cilium/cilium` | Go | From 1.15.0 | 1.15.15, 1.16.8, 1.17.2 | | `github.com/cilium/cilium` | Go | From 1.15.0 | 1.15.15 | | `github.com/cilium/cilium` | Go | From 1.15.0 | 1.15.15 | | `github.com/cilium/cilium` | Go | From 1.16.0 | 1.16.8 | | `github.com/cilium/cilium` | Go | From 1.16.0 | 1.16.8 | | `github.com/cilium/cilium` | Go | From 1.17.0 | 1.17.2 | | `github.com/cilium/cilium` | Go | From 1.17.0 | 1.17.2 | | `cilium` | Bitnami | From 1.15.0 | 1.17.2 | | `cilium-operator` | Bitnami | From 1.15.0 | 1.17.2 | | `hubble-relay` | Bitnami | From 1.15.0 | 1.17.2 | Products: Cilium Cilium. ## How do I fix CVE-2025-30162? Upgrade github.com/cilium/cilium to a fixed version for your release line: 1.15.15, 1.16.8 or 1.17.2. ## Is CVE-2025-30162 being exploited? There is no known exploitation of CVE-2025-30162 in the wild and no public exploit code. ## Other vulnerabilities in cilium - [CVE-2026-49445](https://insights.sbomify.com/CVE-2026-49445/): Cilium: Sensitive information disclosure and cluster disruption via local Envoy admin socket access (critical 9.2) - [CVE-2022-29178](https://insights.sbomify.com/CVE-2022-29178/): Incorrect Default Permissions in Cilium (high 8.8) - [CVE-2024-28860](https://insights.sbomify.com/CVE-2024-28860/): Insecure IPsec transport encryption in Cilium (high 8.0) - [CVE-2026-41520](https://insights.sbomify.com/CVE-2026-41520/): Cillium exposes sensitive information included in the cilium-bugtool debug archive (high 7.9) - [CVE-2024-37307](https://insights.sbomify.com/CVE-2024-37307/): Cilium leaks sensitive information in cilium-bugtool (high 7.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-30162 and fix it if it is affected. What it is: CVE-2025-30162 is a low-severity missing authorization vulnerability in cilium, published on 24 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-30162 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/cilium/cilium (Go): affected from 1.15.0; fixed in 1.15.15, 1.16.8, 1.17.2 - github.com/cilium/cilium (Go): affected from 1.15.0; fixed in 1.15.15 - github.com/cilium/cilium (Go): affected from 1.15.0; fixed in 1.15.15 - github.com/cilium/cilium (Go): affected from 1.16.0; fixed in 1.16.8 - github.com/cilium/cilium (Go): affected from 1.16.0; fixed in 1.16.8 - github.com/cilium/cilium (Go): affected from 1.17.0; fixed in 1.17.2 - github.com/cilium/cilium (Go): affected from 1.17.0; fixed in 1.17.2 - cilium (Bitnami): affected from 1.15.0; fixed in 1.17.2 - cilium-operator (Bitnami): affected from 1.15.0; fixed in 1.17.2 - hubble-relay (Bitnami): affected from 1.15.0; fixed in 1.17.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-30162/ (Markdown: https://insights.sbomify.com/CVE-2025-30162/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30162 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30162 - OSV: https://osv.dev/vulnerability/CVE-2025-30162 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-30162/ Summaries are generated and may contain mistakes; the official description above is the record.