CVE-2025-32793
mediumpriority · track · 16OT risk · elevatedEPSS 0.001 · 4 %ileEUUSEPSS · scored 2026-10-26
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 3.7–4
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (12)
Products and version ranges known to be affected.
advisories (5)
Vendor and ecosystem advisories describing this.
- GHSA-5vxx-c285-pcq4In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters2025-04-21ghsa · osvUS
### 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.
- BIT-cilium-2025-32793Cilium packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters2025-04-23vendor · osvUS
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.
- BIT-cilium-operator-2025-32793Cilium packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters2025-04-23vendor · osvUS
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.
- BIT-hubble-relay-2025-32793Cilium packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters2025-04-23vendor · osvUS
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.
- GO-2025-3635In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters in github.com/cilium/cilium2025-04-22vendor · osvUS
In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters in github.com/cilium/cilium
also known as (8)
Other names and identifiers for this entity.
- CNNVD-202504-3259cnnvd
- EUVD-2025-12230enisa_euvd
- GHSA-5vxx-c285-pcq4enisa_euvd
- BIT-cilium-2025-32793osv
- BIT-cilium-operator-2025-32793osv
- BIT-hubble-relay-2025-32793osv
- GHSA-5vxx-c285-pcq4osv
- GO-2025-3635osv
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/cilium/cilium/pull/38592cnnvd
- https://github.com/cilium/cilium/releasesPatchcnnvd
- https://github.com/cilium/cilium/security/advisories/GHSA-5vxx-c285-pcq4cnnvd
- https://github.com/cilium/cilium/pull/38592enisa_euvd
- https://github.com/cilium/cilium/security/advisories/GHSA-5vxx-c285-pcq4enisa_euvd
- https://github.com/cilium/cilium/pull/38592Patchnvd
- https://github.com/cilium/cilium/security/advisories/GHSA-5vxx-c285-pcq4PatchThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan