CVE-2024-28250: Unencrypted traffic between nodes when using WireGuard and L7 policies
Impact In Cilium clusters with WireGuard enabled and traffic matching Layer 7 policies: - Traffic that should be WireGuard-encrypted is sent unencrypted between a node's Envoy proxy and pods on other nodes. - Traffic that should be WireGuard-encrypted is sent unencrypted between a node's DNS proxy and pods on other nodes.
Published Mar 18, 2024 · Updated Jan 9, 2025
Affected packages
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.14.0, < 1.14.8
- Fixed in
- 1.14.8
- Check
go list -m github.com/cilium/cilium
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.15.0, < 1.15.2
- Fixed in
- 1.15.2
- Check
go list -m github.com/cilium/cilium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
In Cilium clusters with WireGuard enabled and traffic matching Layer 7 policies:
- Traffic that should be WireGuard-encrypted is sent unencrypted between a node's Envoy proxy and pods on other nodes.
- Traffic that should be WireGuard-encrypted is sent unencrypted between a node's DNS proxy and pods on other nodes.
Patches
This issue affects:
- In native routing mode (
routingMode=native): - Cilium v1.14 versions before v1.14.8
- Cilium v1.15 versions before v1.15.2
- In tunneling mode (
routingMode=tunnel): - Cilium v1.14 versions before v1.14.4
- Cilium v1.14.4 if
encryption.wireguard.encapsulateis set tofalse(default).
This issue has been resolved in:
- In native routing mode (
routingMode=native): - Cilium v1.14.8
- Cilium v1.15.2
- In tunneling mode (
routingMode=tunnel): - Cilium v1.14.4. NOTE
encryption.wireguard.encapsulatemust be set totrue.
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 @brb, @giorio94, @gandro and @jschwinger233 for their work on triaging and remediating this issue.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
If you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list where only members of the Cilium internal security team are subscribed to, and your report will be treated as top priority.
Credited to giorio94, brb, jschwinger233.
References
- https://github.com/cilium/cilium/security/advisories/GHSA-v6q2-4qr3-5cw6
- https://nvd.nist.gov/vuln/detail/CVE-2024-28250
- https://github.com/cilium/cilium/releases/tag/v1.13.13
- https://github.com/cilium/cilium/releases/tag/v1.14.8
- https://github.com/cilium/cilium/releases/tag/v1.15.2
- https://github.com/advisories/GHSA-v6q2-4qr3-5cw6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-56742
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
medium5.9Sep 24, 2026CVE-2026-56743
Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
medium5.4Sep 3, 2026CVE-2026-49445
Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access
critical9.2Jul 6, 2026CVE-2026-53935
CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
medium6.9Jul 6, 2026CVE-2026-41520
Cillium exposes sensitive information included in the cilium-bugtool debug archive
high7.9Apr 25, 2026CVE-2026-33726
Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic
medium5.4Mar 26, 2026
