NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-41520: Cillium exposes sensitive information included in the cilium-bugtool debug archive

highCVSS 3.1 7.9GHSA-gj49-89wh-h4gj

Impact The output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled. Users of WireGuard Transparent Encryption are affected. The sensitive data is the WireGuard private key (ciliumwg0.key) used for node-to-node encrypted communication cilium-bugtool is a debugging tool that is typically invoked manually and does not run during the normal…

Published Apr 25, 2026 · Updated May 13, 2026

Affected packages

github.com/cilium/cilium

Ecosystem
Go
Affected
< 1.17.15
Fixed in
1.17.15
Check
go list -m github.com/cilium/cilium

github.com/cilium/cilium

Ecosystem
Go
Affected
>= 1.18.0, < 1.18.9
Fixed in
1.18.9
Check
go list -m github.com/cilium/cilium

github.com/cilium/cilium

Ecosystem
Go
Affected
>= 1.19.0, < 1.19.3
Fixed in
1.19.3
Check
go list -m github.com/cilium/cilium

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled.

Users of WireGuard Transparent Encryption are affected. The sensitive data is the WireGuard private key (cilium_wg0.key) used for node-to-node encrypted communication

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's cilium sysdump command.

Patches

This issue affects:

  • 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

This issue has been patched in:

  • Cilium v1.19.3
  • Cilium v1.18.9
  • Cilium v1.17.15

Workarounds

There is no workaround to this issue.

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.

Acknowledgements

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.

For more information

If there are any questions or comments about this advisory, please reach out on Slack.

Cilium strongly encourages the reporting of suspected vulnerabilities to the security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and the report will be treated as top priority.

Credited to tklauser, kodareef5.

References

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 entries