Skip to main content
CVE-2025-64715VulnerabilityPublished Updated

CVE-2025-64715: github.com/cilium/cilium · Cilium with Misconfigured ToGroups

Affects github.com/cilium/ciliumSource GCVE Database

0

Not known to be exploited · CVSS 4.0 Medium : upgrade to 1.18.4 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.18.4, 1.17.10, 1.16.17
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade github.com/cilium/cilium to 1.18.4; github.com/cilium/cilium to 1.17.10; github.com/cilium/cilium to 1.16.17.

Affected software

ProductAffectedFixed in
Gogithub.com/cilium/ciliumAffected
  • >=1.18.0 <1.18.4
Fixed in
  • 1.18.4
Gogithub.com/cilium/ciliumAffected
  • >=1.17.0 <1.17.10
Fixed in
  • 1.17.10
Gogithub.com/cilium/ciliumAffected
  • <1.16.17
Fixed in
  • 1.16.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is officially patched in Cilium versions 1.18.4, 1.17.10, and 1.16.17. Users should upgrade to these or later versions to remediate the issue. There are no available workarounds. Review and correct any egress policies referencing AWS security group IDs to ensure they reference valid and attached security groups.

Description

### Impact `CiliumNetworkPolicy`s 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. ### Patches This issue has been patched in: * Cilium v1.18.4 * Cilium v1.17.10 * Cilium v1.16.17 ### 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 [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

References

Community reviews

Loading reviews…