Is CVE-2025-64715 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-64715 being exploited in the wild.

How severe is CVE-2025-64715?

Medium severity, with a CVSS score of 4, published 29 November 2025.

Which products and versions are affected?

Cilium >= 1.18.0, = 1.17.0, < 1.17.10; <= 1.16.16; github.com/cilium/cilium (Go) SEMVER:introduced=0,fixed=1.16.17,introduced=1.17.0,fixed=1.17.10,introduced=1.18.0,fixed=1.18.4, SEMVER:introduced=1.18.0,fixed=1.18.4.

Is there a fix for CVE-2025-64715?

Yes. github.com/cilium/cilium (Go): upgrade to 1.18.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-64715 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2025-64715?

Check whether you run Cilium or github.com/cilium/cilium (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-64715: Cilium unrestricted egress traffic via misconfigured AWS toGroups

Q: Is there a fix for CVE-2025-64715?

Yes. github.com/cilium/cilium (Go): upgrade to 1.18.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-64715 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2025-64715?

Check whether you run Cilium or github.com/cilium/cilium (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-64715 · Severity: medium · CVSS 4 · Published 2025-11-29

Cilium is a networking and security tool used to manage traffic between applications in cloud environments. A configuration issue in how it handles AWS security groups can cause network policies to fail silently, potentially allowing applications to communicate with unauthorized external destinations. This could lead to unintended data exposure if outbound traffic is not properly restricted as intended by administrators.

Technologies: Cilium, github.com/cilium/cilium (Go). Vendors: Cilium, Go.

Quick answers

Is CVE-2025-64715 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-64715 being exploited in the wild.
How severe is CVE-2025-64715?: Medium severity, with a CVSS score of 4, published 29 November 2025.
Which products and versions are affected?: Cilium >= 1.18.0, < 1.18.4; >= 1.17.0, < 1.17.10; <= 1.16.16; github.com/cilium/cilium (Go) SEMVER:introduced=0,fixed=1.16.17,introduced=1.17.0,fixed=1.17.10,introduced=1.18.0,fixed=1.18.4, SEMVER:introduced=1.18.0,fixed=1.18.4.
Is there a fix for CVE-2025-64715?: Yes. github.com/cilium/cilium (Go): upgrade to 1.18.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-64715 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2025-64715?: Check whether you run Cilium or github.com/cilium/cilium (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/cilium/cilium (Go): upgrade to 1.18.4 or later
```
go get github.com/cilium/cilium@v1.18.4
```

Technical details

A vulnerability in Cilium's policy engine occurs when a CiliumNetworkPolicy uses 'egress.toGroups.aws.securityGroupsIds' to reference AWS security group IDs that either do not exist or are not attached to any network interface. In these specific scenarios, the 'toCIDRset' section of the derived policy is not generated. This root cause leads to a failure in applying intended egress restrictions, potentially allowing broader outbound access than defined. The issue is classified as Improper Access Control (CWE-284) and has been addressed in versions 1.18.4, 1.17.10, and 1.16.17.

Affected products

Cilium Cilium >= 1.18.0, < 1.18.4; >= 1.17.0, < 1.17.10; <= 1.16.16

Identifiers

CVE-2025-64715
GHSA-38pp-6gcp-rqvm
GO-2025-4167

Timeline

2025-11-27: disclosed
2025-11-29: advisory: NVD publication
2025-12-01: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.