# Talos Linux: Support bundle does not redact registry credentials Advisory record · `GHSA-7cxh-94cf-mfp6` - **Identifiers:** `GHSA-7cxh-94cf-mfp6` · `CVE-2026-77564` - **State:** Confirmed - **Severity:** CVSS 3.3 Low - **Critical:** No - **Weakness (CWE):** [CWE-312](https://cwe.mitre.org/data/definitions/312.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) - **Published:** 15 Oct 2026 - **Updated:** 26 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 15 Oct 2026, 20:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/siderolabs/talos` (Go): affected `<1.14.0-alpha.0.0.20260513110206-76080416beee`; fixed in `1.14.0-alpha.0.0.20260513110206-76080416beee` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Talos Linux support bundles generated by talosctl support include registry authentication credentials from RegistryAuthConfig resources, in the registryconfigs and etcfilespecs files. The Go module github.com/siderolabs/talos is affected before 1.14.0-alpha.0.0.20260513110206-76080416beee, and that version is listed as the fix. An attacker would need access to a support bundle that someone shared publicly, such as on a forum or issue tracker, and could then use the exposed credentials against the private registry. The source notes that Talos 1.14 and later encrypt support bundles by default. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 3.3 Low, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0013, the 2nd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7cxh-94cf-mfp6) ## Sources - [GitHub Advisory Database: GHSA-7cxh-94cf-mfp6](https://github.com/advisories/GHSA-7cxh-94cf-mfp6) - [OSV: GHSA-7cxh-94cf-mfp6](https://osv.dev/vulnerability/GHSA-7cxh-94cf-mfp6) - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .