Rancher Fleet Helm Values are stored inside BundleDeployment in plain text

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2024-52284: 0.24% estimated exploitation activity in the next 30 days; percentile 14.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 1. Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets. 2. 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…

Published by the source

29 Aug 2025, 20:31 UTC

Last modified by the source

29 Aug 2025, 20:31 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6h9x-9j5v-7w9h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52284

Advisory: Rancher Fleet Helm Values are stored inside BundleDeployment in plain text
IDs: CVE-2024-52284, GHSA-6h9x-9j5v-7w9h
Record: https://patchnext.com/advisories/cve-2024-52284 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rancher/fleet 0.13.1-0.20250806151509-088bcbea7edb, 0.12.6, 0.11.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/fleet: affected >= 0.13.0, < 0.13.1-0.20250806151509-088bcbea7edb; >= 0.12.0, < 0.12.6; >= 0.11.0, < 0.11.10; fixed in 0.11.10, 0.13.1-0.20250806151509-088bcbea7edb, 0.12.6

## Suggested inspection (read-only)
- Go github.com/rancher/fleet: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rancher/fleet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6h9x-9j5v-7w9h (GitHub-reviewed advisory GHSA-6h9x-9j5v-7w9h lists affected ranges: Go github.com/rancher/fleet >=0.13.0 =0.12.0 =0.11.0 <0.11.10)

Commands are suggestions: review each one before running it.