Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 17:51 UTC Customize Public modeDiscuss ChangeIntel on Discord

Talos Linux: Support bundle does not redact registry credentials

Exact source revision recorded 26 Oct 2026 15:37:07 UTC. It does not establish the source's current position. Latest evidence.

osv · GHSA-7cxh-94cf-mfp6

Published

### 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 version: 1.35.3 - Platform: amd64

Source published
15 Oct 2026 20:20:16 UTC
Source modified
26 Oct 2026 14:45:05 UTC
Observed here
26 Oct 2026 15:37:07 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Publisher rating · LOW

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 17:51 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current