Advisory record · GHSA-gj49-89wh-h4gj

Cillium exposes sensitive information included in the cilium-bugtool debug archive

CVSS 7.9 HighEPSS 0.0008 · 1st percentile

Published by the GitHub Advisory Database at 25 Apr 2026, 23:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo<1.17.15 || >=1.18.0, <1.18.9 || >=1.19.0, <1.19.31.17.15, 1.18.9, 1.19.3
Identifiers
GHSA-gj49-89wh-h4gj · BIT-cilium-2026-41520 · BIT-cilium-operator-2026-41520 · BIT-hubble-relay-2026-41520 · CVE-2026-41520 · GO-2026-5400
Weakness (CWE)
CWE-200 · CWE-312
Published
25 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Go package github.com/cilium/cilium is affected in versions before 1.17.15, from 1.18.0 before 1.18.9, and from 1.19.0 before 1.19.3. The cilium-bugtool debug archive can include the WireGuard private key on nodes running WireGuard encryption, and anyone who obtains the archive can read that key. Upgrade to 1.17.15, 1.18.9, or 1.19.3. No workaround is listed, but users who have shared archives from WireGuard-enabled nodes should rotate those nodes' WireGuard keys.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.9 High 3.1 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0008, the 1st percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 8 May 2026, 23:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:13 UTC First seen by agentprime
  3. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.