CVE-2026-77564: Talos Linux: Support bundle does not redact registry credentials
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.
Published Oct 15, 2026 · Updated Oct 26, 2026
Affected packages
github.com/siderolabs/talos
- Ecosystem
- Go
- Affected
- < 1.14.0-alpha.0.0.20260513110206-76080416beee
- Fixed in
- 1.14.0-alpha.0.0.20260513110206-76080416beee
- Check
go list -m github.com/siderolabs/talos
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
Credited to Thanzex, zuhairhalawa.
References
- https://github.com/siderolabs/talos/security/advisories/GHSA-7cxh-94cf-mfp6
- https://nvd.nist.gov/vuln/detail/CVE-2026-77564
- https://github.com/siderolabs/talos/pull/13345
- https://github.com/siderolabs/talos/pull/13434
- https://github.com/siderolabs/talos/pull/13611
- https://github.com/siderolabs/talos/commit/4c288caf2de1db7f84bba0539ca5ed7d6ecb9142
- https://github.com/siderolabs/talos/commit/76080416beee6460375c0d0db3cab76cc493ad3e
- https://github.com/siderolabs/talos/commit/7dc716d850e43373ba8702c702105f4edd68fceb
- https://github.com/siderolabs/talos/releases/tag/v1.12.9
- https://github.com/siderolabs/talos/releases/tag/v1.13.3
- https://github.com/advisories/GHSA-7cxh-94cf-mfp6
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
