Advisory record · GHSA-24qp-4xx8-3jvj

Cilium East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers

CVSS 3.2 LowEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 24 Mar 2025, 19:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.16.0, <1.16.8 || >=1.17.0, <1.17.2 || >=1.15.0, <1.15.151.16.8, 1.17.2, 1.15.15
Identifiers
GHSA-24qp-4xx8-3jvj · BIT-cilium-2025-30162 · BIT-cilium-operator-2025-30162 · BIT-hubble-relay-2025-30162 · CVE-2025-30162 · GO-2025-3560
Weakness (CWE)
CWE-863
Published
24 Mar 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Cilium versions 1.15.0 through 1.15.14, 1.16.0 through 1.16.7, and 1.17.0 through 1.17.1 are affected. Network policies that block egress between namespaces do not block traffic from workloads to LoadBalancers created by Gateway API resources, when LB-IPAM or BGP is used. Users should upgrade to Cilium 1.15.15, 1.16.8, or 1.17.2. Users who cannot upgrade may apply a Clusterwide Cilium Network Policy to restrict traffic to the Cilium Ingress Gateway, though the source gives no complete policy.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
3.2 Low 3.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.