MediumGHSA-5vxx-c285-pcq4BIT-cilium-2025-32793BIT-cilium-operator-2025-32793BIT-hubble-relay-2025-32793CVE-2025-32793

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

Published 21 Apr 2025 · Updated 10 Sept 2026

Is your project on an affected github.com/cilium/cilium?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.13.0 <1.15.16
Fixed in
1.15.16
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.15.16
Affected
>=1.16.0 <1.16.9
Fixed in
1.16.9
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.16.9
Affected
>=1.17.0 <1.17.3
Fixed in
1.17.3
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.17.3

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 [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.

Is GHSA-5vxx-c285-pcq4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cilium/cilium, and gives you the command that fixes it.

More advisories for github.com/cilium/cilium

  • LowCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces in github.com/cilium/cilium · 1 Oct 2026
  • MediumCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces · 24 Sept 2026
  • LowCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match in github.com/cilium/cilium · 10 Sept 2026
  • MediumCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match · 3 Sept 2026
  • LowCVE-2026-49445Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access in github.com/cilium/cilium · 7 Jul 2026
  • LowCVE-2026-53935CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation in github.com/cilium/cilium · 7 Jul 2026
All 75 advisories for github.com/cilium/cilium

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.