https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 16:27:40 +0000 https://cve.radiocsirt.org/vuln/bit-cilium-2026-41520 <p><strong>Affected:</strong> Bitnami: cilium</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.15, 1.18.9, and 1.19.3, the output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled. This issue has been patched in versions 1.17.15, 1.18.9, and 1.19.3.</p> <p><strong>Affected:</strong> Bitnami: cilium</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.15, 1.18.9, and 1.19.3, the output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled. This issue has been patched in versions 1.17.15, 1.18.9, and 1.19.3.</p> https://cve.radiocsirt.org/vuln/bit-cilium-2026-41520 https://cve.radiocsirt.org/vuln/euvd-2026-318201 EUVD-2026-318201 https://cve.radiocsirt.org/vuln/euvd-2026-318201 https://cve.radiocsirt.org/vuln/fkie_cve-2026-41520 <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.15, 1.18.9, and 1.19.3, the output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled. This issue has been patched in versions 1.17.15, 1.18.9, and 1.19.3.</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.15, 1.18.9, and 1.19.3, the output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled. This issue has been patched in versions 1.17.15, 1.18.9, and 1.19.3.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-41520 https://cve.radiocsirt.org/vuln/ghsa-gj49-89wh-h4gj <p><strong>Affected:</strong> Go: github.com/cilium/cilium</p> <p>### Impact The output of `cilium-bugtool` can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled.</p> <p>Users of [WireGuard Transparent Encryption](https://docs.cilium.io/en/stable/security/network/encryption-wireguard/) are affected. The sensitive data is the WireGuard private key (`cilium_wg0.key`) used for node-to-node encrypted communication</p> <p>`cilium-bugtool` is a debugging tool that is typically invoked manually and does not run during the normal operation of a Cilium cluster. It is also invoked when gathering sysdumps using the Cilium CLI&#39;s `cilium sysdump` command.</p> <p>### Patches This issue affects:</p> <p>- Cilium v1.19 between v1.19.0 and v1.19.2 inclusive - Cilium v1.18 between v1.18.0 and v1.18.8 inclusive - All versions of Cilium prior to v1.17.15</p> <p>This issue has been patched in:</p> <p>- Cilium v1.19.3 - Cilium v1.18.9 - Cilium v1.17.15</p> <p>### Workarounds There is no workaround to this issue.</p> <p>Users who have previously shared bugtool or sysdump archives from WireGuard-enabled nodes should rotate the WireGuard keys on the affected nodes. This can be done by deleting the key file and restarting the Cilium agent, which will generate a new key pair.</p> <p>### Acknowledgements</p> <p>The Cilium community has worked together with members of Isovalent to prepare these mitigations. Cillium extends special thanks to @kodareef5 for reporting the issue and @tklauser for their work on triaging and remediating this issue.</p> <p>### For more information…</p> <p><strong>Affected:</strong> Go: github.com/cilium/cilium</p> <p>### Impact The output of `cilium-bugtool` can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled.</p> <p>Users of [WireGuard Transparent Encryption](https://docs.cilium.io/en/stable/security/network/encryption-wireguard/) are affected. The sensitive data is the WireGuard private key (`cilium_wg0.key`) used for node-to-node encrypted communication</p> <p>`cilium-bugtool` is a debugging tool that is typically invoked manually and does not run during the normal operation of a Cilium cluster. It is also invoked when gathering sysdumps using the Cilium CLI&#39;s `cilium sysdump` command.</p> <p>### Patches This issue affects:</p> <p>- Cilium v1.19 between v1.19.0 and v1.19.2 inclusive - Cilium v1.18 between v1.18.0 and v1.18.8 inclusive - All versions of Cilium prior to v1.17.15</p> <p>This issue has been patched in:</p> <p>- Cilium v1.19.3 - Cilium v1.18.9 - Cilium v1.17.15</p> <p>### Workarounds There is no workaround to this issue.</p> <p>Users who have previously shared bugtool or sysdump archives from WireGuard-enabled nodes should rotate the WireGuard keys on the affected nodes. This can be done by deleting the key file and restarting the Cilium agent, which will generate a new key pair.</p> <p>### Acknowledgements</p> <p>The Cilium community has worked together with members of Isovalent to prepare these mitigations. Cillium extends special thanks to @kodareef5 for reporting the issue and @tklauser for their work on triaging and remediating this issue.</p> <p>### For more information…</p> https://cve.radiocsirt.org/vuln/ghsa-gj49-89wh-h4gj