Skip to content
Fencer Intel
medium 4.0

CVE-2025-64715 json

Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

published 11mo ago modified 21d ago also BIT-cilium-2025-64715 , BIT-cilium-operator-2025-64715 , BIT-hubble-relay-2025-64715 , EUVD-2025-199886 , GHSA-38pp-6gcp-rqvm , GO-2025-4167

cvss
4.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/cilium/cilium 1.16.17, 1.17.10, 1.18.4
  • bitnami cilium 1.16.17, 1.17.10, 1.18.4
  • bitnami cilium-operator 1.16.17, 1.17.10, 1.18.4
  • bitnami hubble-relay 1.16.17, 1.17.10, 1.18.4
  • cilium cilium 1.16.17, 1.17.10, 1.18.4
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1

suse advisories SUSE-SU-2026:0037-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2025-64715 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
11mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 4.0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cilium/cilium
>=1.18.0, <1.18.4
>=1.17.0, <1.17.10
<1.16.17
1.18.4
1.17.10
1.16.17
bitnami cilium
<1.16.17
>=1.17.0, <1.17.10
>=1.18.0, <1.18.4
1.16.17
1.17.10
1.18.4
bitnami cilium-operator
<1.16.17
>=1.17.0, <1.17.10
>=1.18.0, <1.18.4
1.16.17
1.17.10
1.18.4
bitnami hubble-relay
<1.16.17
>=1.17.0, <1.17.10
>=1.18.0, <1.18.4
1.16.17
1.17.10
1.18.4

Affected products

  • cilium cilium

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.