Skip to main content
VulnerabilityPublished Updated

CVE-2025-64715: cilium · Improper Access Control

Affects ciliumSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.0 Medium · fixed in 1.18.4 : update cilium when convenient.

Data as of 21 Nov 2026, 03:39 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.0
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 29 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 20 Nov 2026.

What to do

Upgrade cilium to 1.18.4, 1.17.10 or 1.16.17.

Affected software

ProductAffectedFixed in
cilium ciliumAffected
  • <1.16.17
  • >=1.17.0 <1.17.10
  • >=1.18.0 <1.18.4
Fixed in
  • 1.16.17
  • 1.17.10
  • 1.18.4

AI-suggested

Apply the official patches by upgrading Cilium to version 1.16.17, 1.17.10, or 1.18.4 or later. There are no workarounds available. Since this is a cloud-hosted service component, ensure the vendor-managed updates are applied promptly.

Description

CVE-2025-64715 is an improper access control vulnerability in Cilium's handling of CiliumNetworkPolicies that reference non-existent or unattached AWS security group IDs in egress rules. This flaw causes the toCIDRset section of the derived policy to be omitted, potentially allowing broader outbound network access than intended. The issue affects Cilium versions prior to 1.16.17, versions from 1.17.0 up to but not including 1.17.10, and versions from 1.18.0 up to but not including 1.18.4. It has been fixed in versions 1.16.17, 1.17.10, and 1.18.4. No workarounds are available.

References

Community reviews

Loading reviews…