CVE-2025-32793: In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters
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.
Published Apr 21, 2025 · Updated Apr 23, 2025
Affected packages
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.13.0, < 1.15.16
- Fixed in
- 1.15.16
- Check
go list -m github.com/cilium/cilium
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.16.0, < 1.16.9
- Fixed in
- 1.16.9
- Check
go list -m github.com/cilium/cilium
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.17.0, < 1.17.3
- Fixed in
- 1.17.3
- Check
go list -m github.com/cilium/cilium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
Credited to julianwiedmann.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-56742
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
medium5.9Sep 24, 2026CVE-2026-56743
Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
medium5.4Sep 3, 2026CVE-2026-49445
Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access
critical9.2Jul 6, 2026CVE-2026-53935
CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
medium6.9Jul 6, 2026CVE-2026-41520
Cillium exposes sensitive information included in the cilium-bugtool debug archive
high7.9Apr 25, 2026CVE-2026-33726
Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic
medium5.4Mar 26, 2026
