# CVE-2026-77564: Talos Linux: Support bundle does not redact registry credentials

Source: https://junglewise.ai/threats/cve-2026-77564-talos-linux-support-bundle-does-not-redact-registry-credentials  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-14  
License: CC BY 4.0 with a link back

CVE-2026-77564 · Severity: low · CVSS 3.3 · Published 2026-10-14

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.

Technologies: [github.com/talos-systems/talos (Go)](https://junglewise.ai/threats/technologies/github-com-talos-systems-talos). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-77564 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-77564 being exploited in the wild.

**How severe is CVE-2026-77564?** Low severity, with a CVSS score of 3.3, published 14 October 2026.

**Which products and versions are affected?** github.com/talos-systems/talos (Go) < 1.14.0-alpha.0.0.20260513110206-76080416beee, SEMVER:introduced=0,fixed=1.14.0-alpha.0.0.20260513110206-76080416beee.

**Is there a fix for CVE-2026-77564?** Yes. github.com/talos-systems/talos (Go): upgrade to 1.14.0-alpha.0.0.20260513110206-76080416beee or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-77564?** Check whether you run github.com/talos-systems/talos (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/talos-systems/talos (Go): upgrade to 1.14.0-alpha.0.0.20260513110206-76080416beee or later

  ```sh
  go get github.com/talos-systems/talos@v1.14.0-alpha.0.0.20260513110206-76080416beee
  ```


## Affected products

- github.com/talos-systems/talos (Go) < 1.14.0-alpha.0.0.20260513110206-76080416beee, SEMVER:introduced=0,fixed=1.14.0-alpha.0.0.20260513110206-76080416beee

## Identifiers

- CVE-2026-77564
- GHSA-7cxh-94cf-mfp6

## Related threats

- [Talos worker join token can be used to get elevated access level to the Talos API](https://junglewise.ai/threats/cve-2022-36103-talos-worker-join-token-can-be-used-to-get-elevated-access-level)
- [Talos vulnerable dependency due to race condition in Linux kernel's IP framework XFRM](https://junglewise.ai/threats/talos-vulnerable-dependency-due-to-race-condition-in-linux-kernel-s-ip-0da741ec)