CVE-2025-30162: East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/cilium/cilium (Go) 1.15.15, 1.16.8, 1.17.2.
Low priority for now. Upgrade to github.com/cilium/cilium (Go) 1.15.15, 1.16.8, 1.17.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-863
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.3
- CNA · GitHub_M
- 3.2
- 1.1 point gap
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| cilium | cilium | cpe:2.3:a:cilium:cilium |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
cilium cilium
- >= 1.16.0, < 1.16.8, >= 1.17.0, < 1.17.2, >= 1.15.0, < 1.15.15affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cilium cilium1.15.0 and later · before 1.15.15
- cilium cilium1.16.0 and later · before 1.16.8
- cilium cilium1.17.0 and later · before 1.17.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/cilium/cilium | from 1.15.0 · before 1.15.15 | 1.15.15 |
| Go | github.com/cilium/cilium | from 1.16.0 · before 1.16.8 | 1.16.8 |
| Go | github.com/cilium/cilium | from 1.17.0 · before 1.17.2 | 1.17.2 |
Same product
cilium: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-27595Cilium eBPF filters may be temporarily removed during agent restart39Monitor
- CVE-2023-39347Cilium NetworkPolicy bypass via pod labels36Monitor
- CVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-23028Jan 22, 2025 · DoS in Cilium agent DNS proxy from crafted DNS responses21Monitor
- ← EarlierCVE-2025-23047Jan 22, 2025 · Cilium vulnerable to information leakage via insecure default Hubble UI CORS header26Monitor
- Later →CVE-2025-30163Mar 24, 2025 · Node based network policies may incorrectly allow workload traffic18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/cilium/cilium | 1.15.15 | Package registry (OSV) |
| Go:github.com/cilium/cilium | 1.16.8 | Package registry (OSV) |
| Go:github.com/cilium/cilium | 1.17.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-53935470 days apartCiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation27Monitor
- CVE-2026-26963332 days apartCilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled21Monitor
- CVE-2026-56743478 days apartCilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match21Monitor
- CVE-2025-301630 days apartNode based network policies may incorrectly allow workload traffic18Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.