How severe is CVE-2024-22032?

No CVSS score has been assigned to CVE-2024-22032 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-22032?

CVE-2024-22032 affects the following packages: github.com/rancher/rancher (Go), github.com/rancher/rancher (Go). Ecosystems affected: Go.

How do I fix CVE-2024-22032?

Update github.com/rancher/rancher to 2.7.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22032 is resolved across your whole dependency graph.

How do I detect CVE-2024-22032 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-22032 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-22032?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-22032 can be triaged on real exposure rather than presence alone.

Is CVE-2024-22032 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-22032 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-22032?

CVE-2024-22032 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-22032?

CVE-2024-22032 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-22032 published, and has it been updated?

CVE-2024-22032 was published on October 16, 2024 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2024-22032 — rancher

CVE-2024-22032 is a Information Exposure vulnerability in github.com/rancher/rancher. A fix is available for github.com/rancher/rancher — see the affected versions and patch details below.

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

Also known asGHSA-q6c7-56cq-g2wmGO-2024-2932

Published

Oct 16, 2024

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-22032.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐹github.com/rancher/rancher🐹github.com/rancher/rancher

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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). 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.

The full custom configuration example:

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 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

If you have any questions or comments about this advisory:

Reach out to the SUSE Rancher Security team for security-related inquiries.
Open an issue in the Rancher repository.
Verify with our support matrix and product support lifecycle.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rancher/rancher`	≥ 2.7.0&&< 2.7.14	2.7.14`go get github.com/rancher/rancher@v2.7.14`
🐹Go	`github.com/rancher/rancher`	≥ 2.8.0&&< 2.8.5	2.8.5`go get github.com/rancher/rancher@v2.8.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/rancher/rancher to 2.7.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22032 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-22032 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-22032. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 t

O3 Security · Impact-Aware SCA

Is CVE-2024-22032 in your dependencies?

O3 Security finds CVE-2024-22032 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVE-2024-22032 — rancher

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2024-22032 in your dependencies?