CVE-2025-64715

This issue affects:

• Cilium v1.18 between v1.18.0 and v1.18.3 inclusive
• Cilium v1.17 between v1.17.0 and v1.17.9 inclusive
• Cilium v1.16.16 and below

Workarounds

There is no workaround to this issue.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @SeanEmac for reporting this issue and to @fristonio for the patch.

For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [email protected]. This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

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.

CVE-2025-64715 has a CVSS score of 4.0 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.18.4, 1.16.17, 1.17.10); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been patched in:

• Cilium v1.18.4
• Cilium v1.17.10
• Cilium v1.16.17

1. What is CVE-2025-64715? CVE-2025-64715 is a medium-severity security vulnerability in github.com/cilium/cilium (go), affecting versions >= 1.18.0, < 1.18.4. It is fixed in 1.18.4, 1.16.17, 1.17.10.
2. How severe is CVE-2025-64715? CVE-2025-64715 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/cilium/cilium are affected by CVE-2025-64715? github.com/cilium/cilium (go) versions >= 1.18.0, < 1.18.4 is affected.
4. Is there a fix for CVE-2025-64715? Yes. CVE-2025-64715 is fixed in 1.18.4, 1.16.17, 1.17.10. Upgrade to this version or later.
5. Is CVE-2025-64715 exploitable, and should I be worried? Whether CVE-2025-64715 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-64715 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-64715?
   • Upgrade github.com/cilium/cilium to 1.18.4 or later
   • Upgrade github.com/cilium/cilium to 1.16.17 or later
   • Upgrade github.com/cilium/cilium to 1.17.10 or later