ghsa-5vxx-c285-pcq4
Vulnerability from github
Impact
When using Wireguard transparent encryption in a Cilium cluster, packets that originate from a terminating endpoint can leave the source node without encryption due to a race condition in how traffic is processed by Cilium.
Patches
This issue has been patched in https://github.com/cilium/cilium/pull/38592.
This issue affects:
- Cilium v1.15 between v1.15.0 and v1.15.15 inclusive
- Cilium v1.16 between v1.16.0 and v1.16.8 inclusive
- Cilium v1.17 between v1.17.0 and v1.17.2 inclusive
This issue is fixed in:
- Cilium v1.15.16
- Cilium v1.16.9
- Cilium v1.17.3
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 @gandro and @pippolo84 for reporting this issue and to @julianwiedmann 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. This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
{ "affected": [ { "package": { "ecosystem": "Go", "name": "github.com/cilium/cilium" }, "ranges": [ { "events": [ { "introduced": "1.13.0" }, { "fixed": "1.15.16" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/cilium/cilium" }, "ranges": [ { "events": [ { "introduced": "1.16.0" }, { "fixed": "1.16.9" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/cilium/cilium" }, "ranges": [ { "events": [ { "introduced": "1.17.0" }, { "fixed": "1.17.3" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-32793" ], "database_specific": { "cwe_ids": [ "CWE-319", "CWE-362" ], "github_reviewed": true, "github_reviewed_at": "2025-04-21T16:17:49Z", "nvd_published_at": "2025-04-21T16:15:54Z", "severity": "MODERATE" }, "details": "### Impact\n\nWhen using [Wireguard transparent encryption](https://docs.cilium.io/en/stable/security/network/encryption-wireguard/#encryption-wg) in a Cilium cluster, packets that originate from a terminating endpoint can leave the source node without encryption due to a race condition in how traffic is processed by Cilium.\n\n### Patches\n\nThis issue has been patched in https://github.com/cilium/cilium/pull/38592.\n\nThis issue affects:\n\n- Cilium v1.15 between v1.15.0 and v1.15.15 inclusive\n- Cilium v1.16 between v1.16.0 and v1.16.8 inclusive\n- Cilium v1.17 between v1.17.0 and v1.17.2 inclusive\n\nThis issue is fixed in:\n\n- Cilium v1.15.16\n- Cilium v1.16.9\n- Cilium v1.17.3\n\n### Workarounds\n\nThere is no workaround to this issue.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @gandro and @pippolo84 for reporting this issue and to @julianwiedmann for the patch.\n\n### For more information\n\nIf 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.", "id": "GHSA-5vxx-c285-pcq4", "modified": "2025-04-23T14:41:18Z", "published": "2025-04-21T16:17:49Z", "references": [ { "type": "WEB", "url": "https://github.com/cilium/cilium/security/advisories/GHSA-5vxx-c285-pcq4" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32793" }, { "type": "WEB", "url": "https://github.com/cilium/cilium/pull/38592" }, { "type": "WEB", "url": "https://github.com/cilium/cilium/commit/e8543eef05126e9ba8a845dc74e96f4e30f6dba9" }, { "type": "PACKAGE", "url": "https://github.com/cilium/cilium" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N", "type": "CVSS_V3" } ], "summary": "In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.