{"id":"CVE-2024-25630","aliases":["GHSA-7496-fgv9-xw82","BIT-cilium-2024-25630","BIT-cilium-operator-2024-25630","BIT-cilium-proxy-2024-25630","BIT-hubble-2024-25630","BIT-hubble-relay-2024-25630","BIT-hubble-ui-2024-25630","BIT-hubble-ui-backend-2024-25630","GO-2024-2568"],"title":"Unencrypted ingress/health traffic when using Wireguard transparent encryption","summary":"Unencrypted ingress/health traffic when using Wireguard transparent encryption","severity":"medium","cvss":6.1,"cvssVector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N","vendor":"cilium","product":"github.com/cilium/cilium","ecosystem":"go","affected":["github.com/cilium/cilium >= 1.14.0, < 1.14.7"],"patched":["github.com/cilium/cilium 1.14.7"],"published":"2024-02-20","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:50:09.750002860Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-7496-fgv9-xw82","references":[{"url":"https://github.com/cilium/cilium/security/advisories/GHSA-7496-fgv9-xw82"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25630"},{"url":"https://docs.cilium.io/en/stable/security/network/encryption-wireguard/#encryption-wg"},{"url":"https://github.com/cilium/cilium"},{"url":"https://github.com/cilium/cilium/releases/tag/v1.14.7"}],"tags":["osv","go"],"epss":0.00184,"epssPercentile":0.08202,"ingestedAt":"2026-09-12T03:13:01.762Z","slug":"CVE-2024-25630","body":"## Overview\n\n### Impact\n\nFor Cilium users who are using CRDs to store Cilium state (the default configuration) and [Wireguard transparent encryption](https://docs.cilium.io/en/stable/security/network/encryption-wireguard/#encryption-wg), responses from pods to the Ingress and health endpoints are not encrypted. Traffic from the Ingress and health endpoints to pods is not affected by this issue. The health endpoint is only used for Cilium's internal health checks.\n\n### Patches\n\nThis issue affects Cilium v1.14 before v1.14.7.\n\nThis issue has been patched in Cilium v1.14.7.\n\n### Workarounds\n\nThere is no workaround to this issue - affected users are encouraged to upgrade.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @gandro for their work on triaging and remediating this issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nIf 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 where only members of the Cilium internal security team are subscribed to, and your report will be treated as top priority.\n\n\n## Affected packages\n\n- `github.com/cilium/cilium >= 1.14.0, < 1.14.7`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/cilium/cilium 1.14.7`","depth":"sunlit","depthScore":34,"depthScoreParts":{"impact":33.6,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}