cilium · Cilium · published 2025-11-29
CVE-2025-64715Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic
Routine No exploitation evidence; EPSS 0.2%.
CVE-2025-64715 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 8% of all CVEs. This Cilium vulnerability: CVSS 4.0 (v3.1). Fixed upstream in Cilium 1.18.4, 1.17.10, 1.16.17. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Cilium 1.18.4, 1.17.10, 1.16.17.
Patch events
OrchestrationCilium
Cilium security releases: 1.18.4, 1.17.10, 1.16.17
Upgrade to
1.18.41.17.101.16.17Why: Vendor security release for server software (most severe: CVE-2025-64715).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (8th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.0 (v3.1)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- cilium cilium
< 1.16.17(affected)>= 1.17.0, < 1.17.10(affected)>= 1.18.0, < 1.18.4(affected)
Description (from the CVE record)#
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.16.17, 1.17.10, and 1.18.4, CiliumNetworkPolicys which use egress.toGroups.aws.securityGroupsIds to reference AWS security group IDs that do not exist or are not attached to any network interface may unintentionally allow broader outbound access than intended by the policy authors. In such cases, the toCIDRset section of the derived policy is not generated, which means outbound traffic may be permitted to more destinations than originally intended. This issue has been patched in versions 1.16.17, 1.17.10, and 1.18.4. There are no workarounds for this issue.
Quoted from the CVE Program record.