Talos
Monthly
Support bundles generated by talosctl on Talos Linux releases prior to 1.12.9 and 1.13.3 include the registry 'auth' field from registryconfigs.cri.talos.dev.yaml and sensitive file content from etcfilespecs.files.talos.dev.yaml without marking or redacting them, so an operator who hands such a bundle to an unintended recipient can expose private container-registry credentials and configuration secrets. The flaw is a locally triggered information-disclosure issue rated CVSS 3.3 (AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N): exploitation requires an operator to produce the bundle and deliberately share it, and the real-world impact depends on the network exposure of the leaked registry and the privileges of the exposed credentials. No public exploit code or confirmed active exploitation has been identified, and the issue is fixed in 1.12.9 and 1.13.3.
Support bundles generated by talosctl on Talos Linux releases prior to 1.12.9 and 1.13.3 include the registry 'auth' field from registryconfigs.cri.talos.dev.yaml and sensitive file content from etcfilespecs.files.talos.dev.yaml without marking or redacting them, so an operator who hands such a bundle to an unintended recipient can expose private container-registry credentials and configuration secrets. The flaw is a locally triggered information-disclosure issue rated CVSS 3.3 (AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N): exploitation requires an operator to produce the bundle and deliberately share it, and the real-world impact depends on the network exposure of the leaked registry and the privileges of the exposed credentials. No public exploit code or confirmed active exploitation has been identified, and the issue is fixed in 1.12.9 and 1.13.3.