CVE-2026-77564: Talos Linux: Support bundle does not redact registry credentials
Talos Linux is a Linux distribution built for Kubernetes deployments. Prior to 1.12.9 and 1.13.3, talosctl support includes the auth field from resources/registryconfigs.cri.talos.dev.yaml and sensitive content from etcfilespecs.files.talos.dev.yaml in generated support bundles instead of marking or redacting those resources. An operator who shares a bundle with an unintended party can therefore disclose private registry authentication parameters, with impact depending on the registry's network exposure and credential privileges. Talos 1.14 and later encrypt support bundles by default, which reduces but does not replace the need for redaction. This issue is fixed in versions 1.12.9 and 1.13.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
talosctlto a version that resolves this vulnerability.Fixed in 1.12.9 - Upgrade
Upgrade
talosctlto a version that resolves this vulnerability.Fixed in 1.13.3
Event History
Frequently Asked Questions
Who is exposed to credential disclosure?
Operators using Talos versions before 1.12.9 or 1.13.3 who generate and share talosctl support bundles are exposed. The practical impact depends on whether the included private registry credentials can reach the registry and what privileges those credentials have.
What user action is required for disclosure?
An operator must generate a support bundle and share it with an unintended party. The vulnerable bundle can include the auth field from registry configuration resources and sensitive content from etc file specification resources.
Are support bundles protected by default in newer releases?
Talos 1.14 and later encrypt support bundles by default. Encryption reduces exposure risk, but it does not replace redaction of sensitive data.
What versions contain the fix?
The issue is fixed in Talos 1.12.9 and 1.13.3.