Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec

CVSS 3.1 6.5 MEDIUMCVSS 4.0 7.1 HIGHEUVD CVSS 4.0 7.1 CVSS 4.0 · [email protected] · Secondary 7.1 HIGHCVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/rancher/rancher 2.7.14Fixed by github.com/rancher/rancher 2.8.5osv · severity unknownKEV status unknown

cve-program · CVE-2024-22032

Published

A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled. When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver.

Read the publisher's advisory

euvd · EUVD-2024-2135

Published

A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled. When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver.

Read the publisher's advisory

nvd · CVE-2024-22032

Published

A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled. When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver.

Read the publisher's advisory

osv · GHSA-q6c7-56cq-g2wm

Published

### Impact This issue is only relevant to clusters provisioned using RKE1 with secrets encryption configuration enabled. A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled (please see the [RKE documentation](https://rke.docs.rancher.com/config-options/secrets-encryption)). When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver. This could lead to an unauthorized user gaining access to the entire secrets encryption config specific for the cluster, only on the applied spec. Since this affects only custom encryption configurations, users need to manually rotate the keys by editing the cluster. For more information, please refer to the [RKE secrets encryption documentation](https://rke.docs.rancher.com/config-options/secrets-encryption#key-rotation). The full custom configuration example: ```yaml services: kube-api: secrets_encryption_config: enabled: true custom_config: apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration resources: - resources: - secrets providers: - aescbc: keys: - name: k-fw5hn secret: RTczRjFDODMwQzAyMDVBREU4NDJBMUZFNDhCNzM5N0I= #<--- needs to be changed - identity: {} ``` Please consult the associated [MITRE ATT&CK - Technique - Unsecured Credentials](https://attack.mitre.org/techniques/T1552/) for further information about this category of attack. ### Patches To address this issue, the fix introduces a new change that copies the AppliedSpec before mutating. As such, the next time the cluster is reconciled and the AppliedSpec is set, all references to sensitive data will be removed. Patched versions include releases `2.7.14` and `2.8.5`. ### Workarounds There are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of RKE/Rancher Manager which contains the fixes. ### References - [CVE-2024-22032](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-22032) If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security-related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

Read the publisher's advisory

osv · GO-2024-2932

Published

Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec in github.com/rancher/rancher. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/rancher/rancher from v2.7.0 before v2.7.14, from v2.8.0 before v2.8.5.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 01:48:38 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

13 Nov 2026 01:25:45 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

11 Nov 2026 00:31:41 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

9 Nov 2026 00:03:50 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

6 Nov 2026 23:06:17 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

4 Nov 2026 22:06:38 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

2 Nov 2026 21:08:23 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

31 Oct 2026 20:16:39 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

29 Oct 2026 19:42:05 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

27 Oct 2026 18:58:53 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

euvd · EUVD-2024-2135 · Published

24 Oct 2026 23:17:22 UTC

A vulnerability has been identified in which an RKE1 cluster keeps

nvd · CVE-2024-22032 · Published

24 Oct 2026 13:19:41 UTC

Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec

osv · GHSA-q6c7-56cq-g2wm · Published

24 Oct 2026 13:19:41 UTC

Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec in github.com/rancher/rancher

osv · GO-2024-2932 · Published

23 Oct 2026 15:48:27 UTC

Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec

cve-program · CVE-2024-22032 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current