🛡️ CVE-2025-32793 — cilium
Description
In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters
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 [[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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity none, availability none.
Weakness class
CVE-2025-32793 is classified as CWE-319: Cleartext Transmission of Sensitive Information. Sensitive data crosses the network without encryption and can be read or altered in transit.
Affected software
CVE-2025-32793 is recorded against 4 packages.
- cilium
- cilium-operator
- github.com/cilium/cilium
- hubble-relay
Timeline and source
Published on 23 April 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| cilium | — | — |
| cilium-operator | — | — |
| github.com/cilium/cilium | — | — |
| hubble-relay | — | — |
References
Similar Threats
- Unknown CLEANSTART-2026-BR79647
- Unknown CLEANSTART-2026-GB36430
- Unknown CLEANSTART-2026-QR52625
- High CVE-2024-28860
- High CVE-2024-28248
More CVE 2025 advisories
Browse all of CVE 2025 in the advisory index.
Vulnerability Monitoring
Track new vulnerabilities in cilium
CVE-2025-32793 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.