Advisory

GHSA-6h9x-9j5v-7w9h

Also known as: CVE-2024-52284, GO-2025-3927

Summary

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text

Details

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

  1. The git job that runs fleet apply will now create secrets for Helm values.
  2. Fleet controller generates bundledeployments and now creates a Helm values secret per bundle deployment in the cluster namespace.
  3. 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:

helm:
  valuesFiles:
    - config-chart/values.yaml # will not be excluded → risky

Use:

helm:
  valuesFiles:
    - values.yaml # will be excluded

References
If you have any questions or comments about this advisory:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-08-29 20:31 UTC
Modified
2025-09-08 14:59 UTC

Affected packages and fixes

github.com/rancher/fleet

Go · All systems

Affected

  • introduced 0.13.0, fixed 0.13.1-0.20250806151509-088bcbea7edb (semver)

Fixed versions

0.13.1-0.20250806151509-088bcbea7edb

Fix

  • Fixed version 0.13.1-0.20250806151509-088bcbea7edb
    go get github.com/rancher/[email protected]

github.com/rancher/fleet

Go · All systems

Affected

  • introduced 0.12.0, fixed 0.12.6 (semver)

Fixed versions

0.12.6

Fix

github.com/rancher/fleet

Go · All systems

Affected

  • introduced 0.11.0, fixed 0.11.10 (semver)

Fixed versions

0.11.10

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences