CVE-2025-32793: Cilium packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters

Published Apr 21, 2025
·
Updated

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.

Other sources

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Versions 1.15.0 to 1.15.15, 1.16.0 to 1.16.8, and 1.17.0 to 1.17.2, are vulnerable 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. This issue has been patched in versions 1.15.16, 1.16.9, and 1.17.3. There are no workarounds available for this issue.

— MITRE

Affected Software

7 affected componentsFixes available
Cilium Cilium>=1.15.0<=1.15.15, >=1.16.0<=1.16.8, >=1.17.0<=1.17.2
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
Cilium Cilium>=1.13.0<1.15.16
Cilium Cilium>=1.16.0<1.16.9
Cilium Cilium>=1.17.0<1.17.3

Event History

Apr 21, 2025
CVE Published
via MITRE·03:34 PM
Data Sourced
via MITRE·03:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
RemedyAffected Software
Advisory Published
via GitHub·04:17 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-32793?

CVE-2025-32793 has been classified with a high severity due to its potential impact on encrypted packet handling in Cilium.

2

How do I fix CVE-2025-32793?

To fix CVE-2025-32793, upgrade Cilium to version 1.15.16, 1.16.9, or 1.17.3 or later.

3

What versions of Cilium are affected by CVE-2025-32793?

CVE-2025-32793 affects Cilium versions 1.15.0 to 1.15.15, 1.16.0 to 1.16.8, and 1.17.0 to 1.17.2.

4

What impact does CVE-2025-32793 have on Cilium clusters?

CVE-2025-32793 can lead to potential exposure of sensitive information due to improper handling of packets with Wireguard encryption.

5

Is there a workaround for CVE-2025-32793 if upgrading is not possible?

Currently, there is no official workaround for CVE-2025-32793, and upgrading is strongly recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203