Most recent entries from all

BIT-cilium-2025-64715 — Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

Affected: Bitnami: cilium

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.

CLEANSTART-2026-EQ27053 — Security fix for CVE-2025-64715 applied in: hubble-ui 0.13.3-r0, hubble-ui-fips 0.13.3-r0

Affected: CleanStart: hubble-ui, CleanStart: hubble-ui-fips

CVE-2025-64715 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.

fkie_cve-2025-64715

GHSA-38pp-6gcp-rqvm — Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

Affected: Go: github.com/cilium/cilium

### 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.