https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 18:28:39 +0000 https://cve.radiocsirt.org/vuln/bdu:2022-05603 bdu:2022-05603 https://cve.radiocsirt.org/vuln/bdu:2022-05603 https://cve.radiocsirt.org/vuln/euvd-2026-167477 EUVD-2026-167477 https://cve.radiocsirt.org/vuln/euvd-2026-167477 https://cve.radiocsirt.org/vuln/fkie_cve-2021-36783 <p>A Insufficiently Protected Credentials vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners and Project Members to read credentials, passwords and API tokens that have been stored in cleartext and exposed via API endpoints. This issue affects: SUSE Rancher Rancher versions prior to 2.6.4; Rancher versions prior to 2.5.13.</p> <p>A Insufficiently Protected Credentials vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners and Project Members to read credentials, passwords and API tokens that have been stored in cleartext and exposed via API endpoints. This issue affects: SUSE Rancher Rancher versions prior to 2.6.4; Rancher versions prior to 2.5.13.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-36783 https://cve.radiocsirt.org/vuln/ghsa-8w87-58w6-hfv8 <p><strong>Affected:</strong> Go: github.com/rancher/rancher</p> <p>### Impact</p> <p>It was discovered that in Rancher versions up to and including 2.5.12 and 2.6.3 there is a failure to properly sanitize credentials in cluster template answers. This failure can lead to plaintext storage and exposure of credentials, passwords and API tokens.</p> <p>The exposed credentials are visible in Rancher to authenticated `Cluster Owners`, `Cluster Members`, `Project Owners` and `Project Members` on the endpoints `/v1/management.cattle.io.clusters`, `/v3/clusters` and `/k8s/clusters/local/apis/management.cattle.io/v3/clusters`.</p> <p>Sensitive fields are now stripped from `Clusters` objects before the object is stored. For objects that existed before this security fix, a one-time migration happens on startup.</p> <p>**Important:** - It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary. - The final impact severity for confidentiality, integrity and availability is dependent on the permissions that the leaked credentials have on their own services.</p> <p>### Patches Patched versions include releases 2.5.13, 2.6.4 and later versions.</p> <p>### Workarounds Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.</p> <p>**Important:** It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary.</p> <p>### For more information If you have any questions or comments about this advisory: * Reach out to [SUSE R…</p> <p><strong>Affected:</strong> Go: github.com/rancher/rancher</p> <p>### Impact</p> <p>It was discovered that in Rancher versions up to and including 2.5.12 and 2.6.3 there is a failure to properly sanitize credentials in cluster template answers. This failure can lead to plaintext storage and exposure of credentials, passwords and API tokens.</p> <p>The exposed credentials are visible in Rancher to authenticated `Cluster Owners`, `Cluster Members`, `Project Owners` and `Project Members` on the endpoints `/v1/management.cattle.io.clusters`, `/v3/clusters` and `/k8s/clusters/local/apis/management.cattle.io/v3/clusters`.</p> <p>Sensitive fields are now stripped from `Clusters` objects before the object is stored. For objects that existed before this security fix, a one-time migration happens on startup.</p> <p>**Important:** - It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary. - The final impact severity for confidentiality, integrity and availability is dependent on the permissions that the leaked credentials have on their own services.</p> <p>### Patches Patched versions include releases 2.5.13, 2.6.4 and later versions.</p> <p>### Workarounds Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.</p> <p>**Important:** It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary.</p> <p>### For more information If you have any questions or comments about this advisory: * Reach out to [SUSE R…</p> https://cve.radiocsirt.org/vuln/ghsa-8w87-58w6-hfv8 https://cve.radiocsirt.org/vuln/gsd-2021-36783 gsd-2021-36783 https://cve.radiocsirt.org/vuln/gsd-2021-36783