https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 12 Oct 2026 17:27:52 +0000 https://cve.radiocsirt.org/vuln/bdu:2022-05660 bdu:2022-05660 https://cve.radiocsirt.org/vuln/bdu:2022-05660 https://cve.radiocsirt.org/vuln/euvd-2026-185344 EUVD-2026-185344 https://cve.radiocsirt.org/vuln/euvd-2026-185344 https://cve.radiocsirt.org/vuln/fkie_cve-2021-36782 <p>A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners, Project Members and User Base to use the Kubernetes API to retrieve plaintext version of sensitive data. This issue affects: SUSE Rancher Rancher versions prior to 2.5.16; Rancher versions prior to 2.6.7.</p> <p>A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners, Project Members and User Base to use the Kubernetes API to retrieve plaintext version of sensitive data. This issue affects: SUSE Rancher Rancher versions prior to 2.5.16; Rancher versions prior to 2.6.7.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-36782 https://cve.radiocsirt.org/vuln/ghsa-g7j7-h4q8-8w2f <p><strong>Affected:</strong> Go: github.com/rancher/rancher</p> <p>### Impact An issue was discovered in Rancher versions up to and including 2.5.15 and 2.6.6 where sensitive fields, like passwords, API keys and Rancher&#39;s service account token (used to provision clusters), were stored in plaintext directly on Kubernetes objects like `Clusters`, for example `cluster.management.cattle.io`. Anyone with read access to those objects in the Kubernetes API could retrieve the plaintext version of those sensitive data.</p> <p>The exposed credentials are visible in Rancher to authenticated `Cluster Owners`, `Cluster Members`, `Project Owners`, `Project Members` and `User Base` on the endpoints: - `/v1/management.cattle.io.catalogs` - `/v1/management.cattle.io.cluster` - `/v1/management.cattle.io.clustertemplates` - `/v1/management.cattle.io.notifiers` - `/v1/project.cattle.io.sourcecodeproviderconfig` - `/k8s/clusters/local/apis/management.cattle.io/v3/catalogs` - `/k8s/clusters/local/apis/management.cattle.io/v3/clusters` - `/k8s/clusters/local/apis/management.cattle.io/v3/clustertemplates` - `/k8s/clusters/local/apis/management.cattle.io/v3/notifiers` - `/k8s/clusters/local/apis/project.cattle.io/v3/sourcecodeproviderconfigs`</p> <p>Sensitive fields are now stripped from `Clusters` and other objects and moved to a `Secret` before the object is stored. The `Secret` is retrieved when the credential is needed. For objects that existed before this security fix, a one-time migration happens on startup.</p> <p>**Important:** - The exposure of Rancher&#39;s `serviceAccountTok…</p> <p><strong>Affected:</strong> Go: github.com/rancher/rancher</p> <p>### Impact An issue was discovered in Rancher versions up to and including 2.5.15 and 2.6.6 where sensitive fields, like passwords, API keys and Rancher&#39;s service account token (used to provision clusters), were stored in plaintext directly on Kubernetes objects like `Clusters`, for example `cluster.management.cattle.io`. Anyone with read access to those objects in the Kubernetes API could retrieve the plaintext version of those sensitive data.</p> <p>The exposed credentials are visible in Rancher to authenticated `Cluster Owners`, `Cluster Members`, `Project Owners`, `Project Members` and `User Base` on the endpoints: - `/v1/management.cattle.io.catalogs` - `/v1/management.cattle.io.cluster` - `/v1/management.cattle.io.clustertemplates` - `/v1/management.cattle.io.notifiers` - `/v1/project.cattle.io.sourcecodeproviderconfig` - `/k8s/clusters/local/apis/management.cattle.io/v3/catalogs` - `/k8s/clusters/local/apis/management.cattle.io/v3/clusters` - `/k8s/clusters/local/apis/management.cattle.io/v3/clustertemplates` - `/k8s/clusters/local/apis/management.cattle.io/v3/notifiers` - `/k8s/clusters/local/apis/project.cattle.io/v3/sourcecodeproviderconfigs`</p> <p>Sensitive fields are now stripped from `Clusters` and other objects and moved to a `Secret` before the object is stored. The `Secret` is retrieved when the credential is needed. For objects that existed before this security fix, a one-time migration happens on startup.</p> <p>**Important:** - The exposure of Rancher&#39;s `serviceAccountTok…</p> https://cve.radiocsirt.org/vuln/ghsa-g7j7-h4q8-8w2f https://cve.radiocsirt.org/vuln/gsd-2021-36782 gsd-2021-36782 https://cve.radiocsirt.org/vuln/gsd-2021-36782