Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77564 low CVSS 3.3

Vulnerability in github.com/talos-systems/talos (CVE-2026-77564)

Summary

Vulnerability in github.com/talos-systems/talos (CVE-2026-77564). Risk of unauthorized operations or information disclosure. Exploitable via auth. Mitigation: upgrade to 1.14.0-alpha.0.0.20260513110206-76080416beee or later.

Original description

The description as published by the source.

Summary

When generating a support bundle with talosctl support the credentials entered for private registries are included in the bundle.

Details

Within the generated support bundle, inside resources/registryconfigs.cri.talos.dev.yaml the auth field of the spec is retained.
The same, potentially sensitive information is present within etcfilespecs.files.talos.dev.yaml.

PoC

Simply run talosctl -n [...] support on a cluster with a RegistryAuthConfig 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 versio…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77564 has been found in github.com/talos-systems/talos.
Attackers can target a specific entry point like auth over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade github.com/talos-systems/talos to 1.14.0-alpha.0.0.20260513110206-76080416beee or later.
If unsure, ask your IT team or search "github.com/talos-systems/talos CVE-2026-77564" on the vendor's site.

CVE-2026-77564 (github.com/talos-systems/talos) — CWE-312 / CVSS v3 3.3
Attack vector: local / unauthenticated
Attack surface: auth / etcfilespecs.files.talos.dev.yaml / RegistryAuthConfig
Patched: 1.14.0-alpha.0.0.20260513110206-76080416beee — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-312) exists in github.com/talos-systems/talos. Attackers reach the vulnerable code path via auth without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/talos-systems/talos. Attack surface: auth / etcfilespecs.files.talos.dev.yaml / RegistryAuthConfig.

🔥 Severity

Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.14.0-alpha.0.0.20260513110206-76080416beee.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/talos-systems/talos' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/talos-systems/talos' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/talos-systems/talos を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/talos-systems/talos to 1.14.0-alpha.0.0.20260513110206-76080416beee

    ステージング環境で 1.14.0-alpha.0.0.20260513110206-76080416beee に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/talos-systems/talos
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.14.0-alpha.0.0.20260513110206-76080416beee"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details