{"id":"CVE-2025-32793","aliases":["GHSA-5vxx-c285-pcq4","BIT-cilium-2025-32793","BIT-cilium-operator-2025-32793","BIT-hubble-relay-2025-32793","GO-2025-3635"],"title":"In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters","summary":"In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters","severity":"medium","cvss":4,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","vendor":"cilium","product":"github.com/cilium/cilium","ecosystem":"go","affected":["github.com/cilium/cilium >= 1.13.0, < 1.15.16","github.com/cilium/cilium >= 1.16.0, < 1.16.9","github.com/cilium/cilium >= 1.17.0, < 1.17.3"],"patched":["github.com/cilium/cilium 1.15.16","github.com/cilium/cilium 1.16.9","github.com/cilium/cilium 1.17.3"],"published":"2025-04-21","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:50:23.531960272Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-5vxx-c285-pcq4","references":[{"url":"https://github.com/cilium/cilium/security/advisories/GHSA-5vxx-c285-pcq4"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-32793"},{"url":"https://github.com/cilium/cilium/pull/38592"},{"url":"https://github.com/cilium/cilium/commit/e8543eef05126e9ba8a845dc74e96f4e30f6dba9"},{"url":"https://github.com/cilium/cilium"}],"tags":["osv","go"],"epss":0.0014,"epssPercentile":0.0373,"ingestedAt":"2026-09-12T03:13:01.756Z","slug":"CVE-2025-32793","body":"## Overview\n\n### 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.\n\n## Affected packages\n\n- `github.com/cilium/cilium >= 1.13.0, < 1.15.16`\n- `github.com/cilium/cilium >= 1.16.0, < 1.16.9`\n- `github.com/cilium/cilium >= 1.17.0, < 1.17.3`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/cilium/cilium 1.15.16`\n- `github.com/cilium/cilium 1.16.9`\n- `github.com/cilium/cilium 1.17.3`","depth":"sunlit","depthScore":22,"depthScoreParts":{"impact":22,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}