CVE-2026-77564
Talos Linux is a Linux distribution built for Kubernetes deployments.
Published Oct 14, 2026 · corrected/updated Oct 15, 2026 · evidence confidence high
### Summary When generating a support bundle with the credentials entered for private registries are included in the bundle. ### Details Within the generated support bundle, inside the field of the spec is retained. The same, potentially sensitive information is present within . ### PoC Simply run on a cluster with a 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
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-77564 is a low public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: github.com/talos-systems/talos (< 1.14.0-alpha.0.0.20260513110206-76080416beee); github.com. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 3.3, EPSS 0.1%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-312. Sources contributing to this record: cve_org, epss, github, gitlab. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 14, 2026 · NIST NVD
Detected
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 d
Oct 15, 2026 · GitHub Advisory Database
Updated
### Summary When generating a support bundle with the credentials entered for private registries are included in the bundle. ### Details Within the generated support bundle, inside the field of the spec is retained. The same, potentially sensitive information is present within . ### PoC Simply run on a cluster with a resource ### Impact The problem itself is minor, however, anyone who has ever upl
Affected
- go github.com/talos-systems/talos< 1.14.0-alpha.0.0.20260513110206-76080416beee
- golang github.comversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-77564
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-77564
30-day exploitation probability 0.1%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-7cxh-94cf-mfp6
Talos Linux: Support bundle does not redact registry credentials
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-77564
When generating a support bundle with talosctl support the credentials entered for private registries are included in the bundle.
advisories.gitlab.com - NIST NVDVulnerability recordCVE-2026-77564
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 i
nvd.nist.gov