CVE-2026-77564: Talos Linux · Support bundle does not redact registry credentials
Affects github.com/siderolabs/talosSource GCVE Database
Not known to be exploited · CVSS 3.3 Low : upgrade to 1.14.0-alpha.0.0.20260513110206-76080416beee when convenient.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.14.0-alpha.0.0.20260513110206-76080416beee
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade github.com/siderolabs/talos to 1.14.0-alpha.0.0.20260513110206-76080416beee.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/siderolabs/talos | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Summary When generating a support bundle with `talosctl support` the credentials entered for private registries are included in the bundle. ### Details Within the generated support bundle, inside `resources/registryconfigs.cri.talos.dev.yaml` the `auth` field of the spec is retained. The same, potentially sensitive information is present within `etcfilespecs.files.talos.dev.yaml`. ### PoC Simply run `talosctl -n [...] support` on a cluster with a `RegistryAuthConfig` resource ### Impact The problem itself is minor, however, anyone who has ever uploaded a support.zip bundle on a github issue, slack thread or public forum could have potentially leaked their internal authentication parameters for a private registry. In most situations, if the network and credentials are set correctly, this should not be a problem. On the other hand, if the affected registry is publicly accessible, and the provided credentials have write access to it, this could lead to possibly serious consequences, from denial of service, to data loss and possibly existing tag hijacking leading to supply chain compromise, for the affected parties which were under the impression that the support bundle is redacted of sensitive information and thus can be shared publicly. ### Notes Talos 1.14+ by default encrypts the support bundle to the age recipients specified (defaulting to siderolabs GitHub org members), so the impact is even lower. ### Environment - Talos version: v1.13.0 - Kubernetes version: 1.35.3 - Platform: amd64
References
- github.com/siderolabs/talos/security/advisories/GHSA-7cxh-94cf-mfp6 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-77564 (opens in a new tab)
- github.com/siderolabs/talos/pull/13345 (opens in a new tab)
- github.com/siderolabs/talos/pull/13434 (opens in a new tab)
- github.com/siderolabs/talos/pull/13611 (opens in a new tab)
- github.com/siderolabs/talos/commit/4c288caf2de1db7f84bba0539ca5ed7d6ecb9142 (opens in a new tab)
- github.com/siderolabs/talos/commit/76080416beee6460375c0d0db3cab76cc493ad3e (opens in a new tab)
- github.com/siderolabs/talos/commit/7dc716d850e43373ba8702c702105f4edd68fceb (opens in a new tab)
- github.com/siderolabs/talos (opens in a new tab)
- github.com/siderolabs/talos/releases/tag/v1.12.9 (opens in a new tab)
- github.com/siderolabs/talos/releases/tag/v1.13.3 (opens in a new tab)