github.com/rancher/fleet

CVE-2024-52284

CVE-2024-52284 is a high-severity security vulnerability in github.com/rancher/fleet (go), affecting versions >= 0.13.0, < 0.13.1-0.20250806151509-088bcbea7edb. It is fixed in 0.13.1-0.20250806151509-088bcbea7edb, 0.12.6, 0.11.10.

Key facts
CVSS score
7.7
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/rancher/fleet
Fixed in
0.13.1-0.20250806151509-088bcbea7edb, 0.12.6, 0.11.10
Disclosed
2024

Summary

Impact A vulnerability has been identified when using Fleet to manage Helm charts where sensitive information is passed through BundleDeployment.Spec.Options.Helm.Values may be stored in plain text. This can result in: Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets. Lack of encryption at rest: BundleDeployment is not configured for Kubernetes encryption at rest by default, causing sensitive values to remain unencrypted within the cluster datastore. This behavior differs from Helm v3’s default approach, where chart state, including values, is stored in Kubernetes secrets, benefiting from built-in protection mechanisms. In affected scenarios, credentials and other sensitive information are exposed both at rest and in responses to API calls. Please consult the associated MITRE ATT&CK - Technique - Credentials from Password Stores for further information about this category of attack. For the exposure of credentials not related to Rancher, the final impact severity for confidentiality, integrity, and availability is dependent on the permissions that the leaked credentials have on their own services. It is recommended to review the potentially exposed sensitive data in this scenario and change secrets, tokens, and passwords as necessary. Patches This vulnerability is addressed by adding the capability for each Bundle and BundleDeployment to have a secret to store options in. The git job that runs fleet apply will now create secrets for Helm values. Fleet controller generates bundledeployments and now creates a Helm values secret per bundle deployment in the cluster namespace. Fleet agent uses the bundledeployment for options, the content resource and the secret to deploy the bundle. Patched versions of Fleet include releases v0.14.0, v0.13.1, v0.12.6 and v0.11.10. Workarounds If you can't upgrade to a fixed version, please make sure to specify paths to valuesFiles as simple file names, e.g.: Instead of: Use: References 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.

Impact

Severity and exposure

CVE-2024-52284 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (0.13.1-0.20250806151509-088bcbea7edb, 0.12.6, 0.11.10). Upgrading removes the vulnerable code path.

Affected versions

go

  • github.com/rancher/fleet (>= 0.13.0, < 0.13.1-0.20250806151509-088bcbea7edb)
  • github.com/rancher/fleet (>= 0.12.0, < 0.12.6)
  • github.com/rancher/fleet (>= 0.11.0, < 0.11.10)

Security releases

  • github.com/rancher/fleet → 0.13.1-0.20250806151509-088bcbea7edb (go)
  • github.com/rancher/fleet → 0.12.6 (go)
  • github.com/rancher/fleet → 0.11.10 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2024-52284 is reachable in your applications. Explore open-source security for your team.

See if CVE-2024-52284 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2024-52284 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade github.com/rancher/fleet to 0.13.1-0.20250806151509-088bcbea7edb or later
  • Upgrade github.com/rancher/fleet to 0.12.6 or later
  • Upgrade github.com/rancher/fleet to 0.11.10 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2024-52284

What is CVE-2024-52284?

CVE-2024-52284 is a high-severity security vulnerability in github.com/rancher/fleet (go), affecting versions >= 0.13.0, < 0.13.1-0.20250806151509-088bcbea7edb. It is fixed in 0.13.1-0.20250806151509-088bcbea7edb, 0.12.6, 0.11.10.

How severe is CVE-2024-52284?

CVE-2024-52284 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/rancher/fleet are affected by CVE-2024-52284?

github.com/rancher/fleet (go) versions >= 0.13.0, < 0.13.1-0.20250806151509-088bcbea7edb is affected.

Is there a fix for CVE-2024-52284?

Yes. CVE-2024-52284 is fixed in 0.13.1-0.20250806151509-088bcbea7edb, 0.12.6, 0.11.10. Upgrade to this version or later.

Is CVE-2024-52284 exploitable, and should I be worried?

Whether CVE-2024-52284 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2024-52284 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-52284?
  • Upgrade github.com/rancher/fleet to 0.13.1-0.20250806151509-088bcbea7edb or later
  • Upgrade github.com/rancher/fleet to 0.12.6 or later
  • Upgrade github.com/rancher/fleet to 0.11.10 or later

Stop the waste.
Protect your environment with Kodem.