cve.bz

CVE-2026-77564 siderolabs talos

3.3 lowEPSS 0.1%Fix available

Low (3.3) in siderolabs talos. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/siderolabs/talos 1.14.0-alpha.0.0.20260513110206-76080416beee.

On this page
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.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-312 Cleartext Storage of Sensitive Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/siderolabs/talos (Go): fixed in 1.14.0-alpha.0.0.20260513110206-76080416beee

Ask an AI about this CVE

Show the promptExplain CVE-2026-77564 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77564?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77564?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77564 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
siderolabs talos< 1.12.9
siderolabs talos>= 1.13.0, < 1.13.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7cxh-94cf-mfp6Gogithub.com/siderolabs/talos<1.14.0-alpha.0.0.20260513110206-76080416beee1.14.0-alpha.0.0.20260513110206-76080416beee

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON