Advisory

GHSA-5vxx-c285-pcq4

Also known as: BIT-cilium-2025-32793, BIT-cilium-operator-2025-32793, BIT-hubble-relay-2025-32793, CVE-2025-32793, GO-2025-3635

Summary

In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-04-21 16:17 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/cilium/cilium

Go · All systems

Affected

  • introduced 1.13.0, fixed 1.15.16 (semver)

Fixed versions

1.15.16

Fix

github.com/cilium/cilium

Go · All systems

Affected

  • introduced 1.16.0, fixed 1.16.9 (semver)

Fixed versions

1.16.9

Fix

github.com/cilium/cilium

Go · All systems

Affected

  • introduced 1.17.0, fixed 1.17.3 (semver)

Fixed versions

1.17.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences