First published: Mon Apr 21 2025(Updated: )
### Impact When 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. ### 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](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/cilium/cilium | >=1.17.0<1.17.3 | 1.17.3 |
go/github.com/cilium/cilium | >=1.16.0<1.16.9 | 1.16.9 |
go/github.com/cilium/cilium | >=1.13.0<1.15.16 | 1.15.16 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of GHSA-5vxx-c285-pcq4 is classified as high due to potential unencrypted packet transmission.
To fix GHSA-5vxx-c285-pcq4, upgrade to Cilium version 1.17.3, 1.16.9, or 1.15.16 depending on your current version.
GHSA-5vxx-c285-pcq4 affects Cilium versions 1.17.0 to 1.17.3, 1.16.0 to 1.16.9, and 1.13.0 to 1.15.16.
The impact of GHSA-5vxx-c285-pcq4 in Cilium clusters is that packets may leave the source node unencrypted due to a race condition.
There is no documented workaround for GHSA-5vxx-c285-pcq4; the recommended action is to update to a secure version.