Every CVE Search/ Get API key

CVE-2024-52284

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text

7.7 HighFix available

Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
None

Exploit likelihood

0.24%Up 0.2 points since Sep 2, 2025
90%50%10%1%

What each source reports

CVE List Score used 7.7

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text

Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets.

Record
CVE-2024-52284
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-312
Updated
2026-11-02
EUVDEUVD-2024-54941 7.7

Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets.

Record
EUVD-2024-54941
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-6h9x-9j5v-7w9h 7.7

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text

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:

Record
GHSA-6h9x-9j5v-7w9h
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-312
Updated
2026-11-02
NVD 7.7

Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets.

Record
CVE-2024-52284
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-312
Updated
2026-11-02
OSVGHSA-6h9x-9j5v-7w9h 7.7

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text

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:

Record
GHSA-6h9x-9j5v-7w9h
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-312
Updated
2026-11-02
OSVUBUNTU-CVE-2024-52284 7.7

Unauthorized disclosure of sensitive data: Any user with GET or LIST permissions on BundleDeployment resources could retrieve Helm values containing credentials or other secrets.

Record
UBUNTU-CVE-2024-52284
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Updated
2026-11-02
Show 4 moreShow less
OSVGO-2025-3927 No score

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text in github.com/rancher/fleet

Rancher Fleet Helm Values are stored inside BundleDeployment in plain text in github.com/rancher/fleet

Record
GO-2025-3927
Updated
2026-11-02
OSVopenSUSE-SU-2025:15538-1 No score

govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media

These are all security issues fixed in the govulncheck-vulndb-0.0.20250908T141310-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15538-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
  • GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
  • GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
  • GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
  • GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
  • GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
  • GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
  • GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
  • GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
  • GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
  • GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
  • GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
  • GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
  • GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
  • GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
  • GO-2026-5933 GHSA-3g4q-2f67-2gvh
  • GO-2026-5934 GHSA-59qp-cfj3-rp64
  • GO-2026-5935 GHSA-7856-g3gv-9wq8
  • GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
  • GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
  • GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
  • GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
  • GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
  • GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
  • GO-2026-5942 CVE-2026-46600
  • GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
  • GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
  • GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
  • GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
  • GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
  • GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
  • GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
  • GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
  • GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
  • GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
  • GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
  • GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
  • GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
  • GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
  • GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
  • GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
  • GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
  • GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
  • GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
  • GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
  • GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
  • GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
  • GO-2026-5969 GHSA-g936-7jqj-mwv8
  • GO-2026-5970 CVE-2026-56852
  • GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
  • GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
  • GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
  • GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
  • GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
  • GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
  • GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
  • GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
  • GO-2026-5981 GHSA-mqxv-9rm6-w8qc
  • GO-2026-5982 GHSA-pqg7-v6wh-3pfp
  • GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
  • GO-2026-5985 GHSA-7rx3-5wx3-5v76
  • GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
  • GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
  • GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
  • GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
  • GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
  • GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
  • GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
  • GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
  • GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
  • GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
  • GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
  • GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
  • GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
  • GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
  • GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
  • GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
Record
openSUSE-SU-2026:21483-1
Updated
2026-11-02
OSVSUSE-SU-2025:03289-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20250918T182144 2025-09-18T18:21:44Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3915 CVE-2025-5187 GHSA-4x4m-3c2p-qppc
    • GO-2025-3956 CVE-2025-47906 CVE-2025-47906

  • Update to version 0.0.20250917T170349 2025-09-17T17:03:49Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3922 CVE-2025-58058 GHSA-jc7w-c686-c4v9
    • GO-2025-3926 CVE-2025-58158 GHSA-w469-hj2f-jpr5
    • GO-2025-3929 CVE-2025-58157 GHSA-9fvj-xqr2-xwg8
    • GO-2025-3938 CVE-2025-58437 GHSA-j6xf-jwrj-v5qp
    • GO-2025-3939 CVE-2025-7445 GHSA-rcw7-pqfp-735x
    • GO-2025-3940 CVE-2025-58445 GHSA-xh7v-965r-23f7
    • GO-2025-3941 CVE-2025-58450 GHSA-p46v-f2x8-qp98
    • GO-2025-3942 CVE-2025-58063 GHSA-93mf-426m-g6x9
    • GO-2025-3943 CVE-2025-58430 GHSA-rf24-wg77-gq7w
    • GO-2025-3944 CVE-2025-54123 GHSA-r4h8-hfp2-ggmf
    • GO-2025-3945 CVE-2025-54376 GHSA-jxmr-2h4q-rhxp
    • GO-2025-3949 CVE-2025-59361 GHSA-2gcv-3qpf-c5qr
    • GO-2025-3950 CVE-2025-9076 GHSA-3vcm-c42p-3hhf
    • GO-2025-3951 CVE-2025-59358 GHSA-2gg8-85m5-8r2p
    • GO-2025-3952 CVE-2025-59359 GHSA-369h-6j28-wwcg
    • GO-2025-3953 CVE-2025-8396 GHSA-p768-c3pr-6459
    • GO-2025-3954 CVE-2025-59360 GHSA-xv9f-728h-9jgv
    • GO-2025-3958 CVE-2025-9072 GHSA-69j8-prx2-vx98
    • GO-2025-3959 CVE-2025-9078 GHSA-9p92-x77w-9fw2
    • GO-2025-3960 CVE-2025-9084 GHSA-hm95-jx66-g2gh
    • GO-2025-3961 CVE-2025-4953 GHSA-m68q-4hqr-mc6f

  • Update to version 0.0.20250908T141310 2025-09-08T14:13:10Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3916 CVE-2025-51667 GHSA-f2m2-4q6r-cwc4
    • GO-2025-3917 CVE-2025-53884 GHSA-8ff6-pc43-jwv3
    • GO-2025-3918 CVE-2025-8077 GHSA-8pxw-9c75-6w56
    • GO-2025-3919 CVE-2025-54467 GHSA-w54x-xfxg-4gxq
    • GO-2025-3920 GHSA-vxg3-w9rv-rhr2
    • GO-2025-3921 GHSA-3rw9-wmc8-8948
    • GO-2025-3923 CVE-2024-58259 GHSA-4h45-jpvh-6p5j
    • GO-2025-3924 CVE-2025-6203 GHSA-8f82-53h8-2p34
    • GO-2025-3925 GHSA-v2ch-c8v8-fgr7
    • GO-2025-3927 CVE-2024-52284 GHSA-6h9x-9j5v-7w9h
    • GO-2025-3930 CVE-2025-58355 GHSA-33pr-m977-5w97
    • GO-2025-3934 CVE-2025-55190 GHSA-786q-9hcg-v9ff
    • GO-2025-3935 CVE-2025-9566 GHSA-wp3j-xq48-xpjw
    • GO-2025-3936 CVE-2025-56760 GHSA-78j5-8vq7-jxv5
    • GO-2025-3937 CVE-2025-56761 GHSA-cgrg-86m5-xm4w
Record
SUSE-SU-2025:03289-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/rancher/fleet
Go
 0.13.0 up to 0.13.1-0.20250806151509-088bcbea7edb
0.13.1-0.20250806151509-088bcbea7edb
github.com/rancher/fleet
Go
 0.12.0 up to 0.12.6
0.12.6
github.com/rancher/fleet
Go
 0.11.0 up to 0.11.10
0.11.10
github.com/rancher/fleet
Go
 0.11.0 up to 0.11.10, 0.12.0 up to 0.12.6, 0.13.0 up to 0.13.1-0.20250806151509-088bcbea7edb
0.11.100.12.60.13.1-0.20250806151509-088bcbea7edb
govulncheck-vulndb
SUSE:Linux Enterprise Module for Package Hub 15 SP6
 before 0.0.20250918T182144-150000.1.107.1
0.0.20250918T182144-150000.1.107.1
govulncheck-vulndb
openSUSE:Leap 15.6
 before 0.0.20250918T182144-150000.1.107.1
0.0.20250918T182144-150000.1.107.1
fleet
Ubuntu:16.04:LTS
 All versions, plus listed versions
0.11.5+dfsg-1
 None known
govulncheck-vulndb
openSUSE:Tumbleweed
 before 0.0.20250908T141310-1.1
0.0.20250908T141310-1.1
govulncheck-vulndb
openSUSE:Leap 16.0
 before 0.0.20260723T184607-160000.1.1
0.0.20260723T184607-160000.1.1

History

History
RecordedChangedSources
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2024-52284 is a high vulnerability (CVSS 7.7) in Suse Rancher, published August 29, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.24%, the 14th percentile. Fixed in github.com/rancher/fleet 0.13.1-0.20250806151509-088bcbea7edb.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 1,542 references and the rest of 1 source description. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open