CVE-2026-77564

Awaiting Analysis Awaiting Analysis - Queue

Information Disclosure in Talos Linux Support Bundles

Publication date: 2026-10-14

Last updated on: 2026-10-16

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-16

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-77564

EUVD

EUVD-2026-101424

Affected Vendors & Products

Vendor	Product	Version / Range
siderolabs	talos	< 1.12.9
siderolabs	talos	>= 1.13.0, < 1.13.3

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-312	The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

Attack-Flow Graph

Executive Summary

CVE-2026-77564 affects Talos Linux, a Kubernetes-focused OS. Prior to versions 1.12.9 and 1.13.3, support bundles generated by talosctl included sensitive registry authentication details in plaintext. This occurred because the auth field from registryconfigs.cri.talos.dev.yaml and sensitive content from etcfilespecs.files.talos.dev.yaml were not redacted. Talos 1.14+ encrypts support bundles by default, but earlier versions require manual redaction to prevent credential leaks.

Detection Guidance

Check support bundle contents for plaintext registry credentials in files like resources/registryconfigs.cri.talos.dev.yaml and etcfilespecs.files.talos.dev.yaml. Use commands like grep -r 'registry' /var/lib/talos/support or inspect generated bundles manually.

Impact Analysis

If you share a support bundle containing registry credentials, an unintended party could access them. If the registry is publicly exposed and credentials have write permissions, attackers could cause denial of service, data loss, or supply chain attacks. The impact depends on registry exposure and credential privileges. The vulnerability requires user interaction to share bundles and has low severity (CVSS 3.3).

Compliance Impact

This vulnerability could lead to unauthorized disclosure of registry credentials and other sensitive data if support bundles are shared improperly. Under GDPR, this may constitute a breach requiring notification if personal data is exposed. For HIPAA, exposure of credentials could risk unauthorized access to protected health information if registry permissions allow it.

Mitigation Strategies

Upgrade Talos to versions 1.12.9, 1.13.3, or later. Avoid sharing support bundles publicly. For versions before 1.14, manually redact sensitive fields in bundles before sharing.

Hi! I’m here to help you understand CVE-2026-77564. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70