Cross-namespace policy bypass via ingress source substitution
Published Mar 24, 2025 · Updated Mar 24, 2025
Incorrect authorization in affected Cilium releases allows local users to reach policy-blocked Gateway API load balancers. The L7 load-balancing proxy uses the ingress IP as the upstream source address and fails to apply the available source pod egress policy. Exposure requires Gateway API Ingress, LB-IPAM or BGP load-balancer implementation, and cross-namespace egress policy; ordinary LoadBalancer resources are unaffected.
Summary
What happened
Incorrect authorization in affected Cilium releases allows local users to reach policy-blocked Gateway API load balancers. The L7 load-balancing proxy uses the ingress IP as the upstream source address and fails to apply the available source pod egress policy. Exposure requires Gateway API Ingress, LB-IPAM or BGP load-balancer implementation, and cross-namespace egress policy; ordinary LoadBalancer resources are unaffected.
The record
- CVE
- CVE-2025-30162
- Published
- Mar 24, 2025
- Updated
- Mar 24, 2025
- Vendor
- Cilium
- Product
- Cilium
- Classifications
- CWE-863
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.15.0, < 1.15.15
- Affected versionversion=>= 1.16.0, < 1.16.8
- Affected versionversion=>= 1.17.0, < 1.17.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo