Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
10.0
Rancher exposes sensitive credentials in older versions
GHSA-8w87-58w6-hfv8
CVE-2021-36783
Summary
If you're using Rancher 2.5.12 or earlier, or 2.6.3 or earlier, sensitive data like passwords and API tokens might be visible to authorized users. To fix this, update to Rancher 2.5.13 or later, or 2.6.4 or later. Review your credentials and change them if necessary to protect your system's security.
What to do
- Update github.com rancher to version 2.5.13.
- Update github.com rancher to version 2.6.4.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| github.com | rancher | > 2.5.0 , <= 2.5.12 | 2.5.13 |
| github.com | rancher | > 2.6.0 , <= 2.6.3 | 2.6.4 |
| suse | rancher | > 2.5.0 , <= 2.5.13 | – |
| suse | rancher | > 2.6.0 , <= 2.6.4 | – |
Original title
Rancher doesn't properly sanitize credentials in cluster template answers
Original description
### Impact
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.
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`.
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.
**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.
### Patches
Patched versions include releases 2.5.13, 2.6.4 and later versions.
### Workarounds
Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.
**Important:** It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary.
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
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.
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`.
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.
**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.
### Patches
Patched versions include releases 2.5.13, 2.6.4 and later versions.
### Workarounds
Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.
**Important:** It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary.
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
ghsa CVSS3.1
10.0
Vulnerability type
CWE-200
Information Exposure
CWE-312
Cleartext Storage of Sensitive Information
CWE-522
Insufficiently Protected Credentials
Published: 3 Mar 2026 · Updated: 7 Mar 2026 · First seen: 6 Mar 2026