Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.3amended

Talos Linux: Support bundle does not redact registry credentials

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/talos-systems/talos 1.14.0-alpha.0.0.20260513110206-76080416beee; github.com/siderolabs/talos 1.14.0-alpha.0.0.20260513110206-76080416beee), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-77564: 0.13% estimated exploitation activity in the next 30 days; percentile 2.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from osv record GHSA-7cxh-94cf-mfp6

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-7cxh-94cf-mfp6

  3. Revision 2 · amended ·

    Amended from ghsa record GHSA-7cxh-94cf-mfp6

  4. Revision 1 · created ·

    Published from osv record GHSA-7cxh-94cf-mfp6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-77564

Advisory: Talos Linux: Support bundle does not redact registry credentials
IDs: CVE-2026-77564, GHSA-7cxh-94cf-mfp6
Record: https://patchnext.com/advisories/cve-2026-77564 (revision 4, source checked 27 Oct 2026, 06:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/talos-systems/talos 1.14.0-alpha.0.0.20260513110206-76080416beee; github.com/siderolabs/talos 1.14.0-alpha.0.0.20260513110206-76080416beee. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/talos-systems/talos: affected < 1.14.0-alpha.0.0.20260513110206-76080416beee; fixed in 1.14.0-alpha.0.0.20260513110206-76080416beee
- Go github.com/siderolabs/talos: affected < 1.14.0-alpha.0.0.20260513110206-76080416beee; fixed in 1.14.0-alpha.0.0.20260513110206-76080416beee

## Suggested inspection (read-only)
- Go github.com/talos-systems/talos: check the installed version with your package manager.
- Go github.com/siderolabs/talos: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/talos-systems/talos, github.com/siderolabs/talos.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7cxh-94cf-mfp6 (OSV record GHSA-7cxh-94cf-mfp6 lists affected ranges: Go github.com/talos-systems/talos >=0 <1.14.0-alpha.0.0.20260513110206-76080416beee (fixed))
- Verified: https://github.com/advisories/GHSA-7cxh-94cf-mfp6 (GitHub-reviewed advisory GHSA-7cxh-94cf-mfp6 lists affected ranges: Go github.com/siderolabs/talos >=0 <1.14.0-alpha.0.0.20260513110206-76080416beee)
- Verified: https://osv.dev/vulnerability/GHSA-7cxh-94cf-mfp6 (OSV record GHSA-7cxh-94cf-mfp6 lists affected ranges: Go github.com/siderolabs/talos >=0 <1.14.0-alpha.0.0.20260513110206-76080416beee (fixed))

Commands are suggestions: review each one before running it.

Loading voting…