Tuesday, August 11, 2026
LIVEThe Unrelenting Cyber Battle: Hacking Threats and the Imperative of Robust Data Protection///Navigating the Cyber Labyrinth: Bolstering Defenses Against Evolving Hacking Threats///The Dual Front War: Battling Hacking and Bolstering Data Protection in the Digital Age///The Ever-Evolving Cyber Threat Landscape: Navigating Hacking and Fortifying Data Protection///The Unseen Battle: Fortifying Data in an Age of Relentless Hacking///The Unseen War: Hacking's Relentless Advance and the Imperative of Data Protection///The Evolving Threat Landscape: Hacking, Data Protection, and the Imperative for Proactive Security///Navigating the Digital Minefield: Bolstering Data Protection in an Era of Relentless Hacking///The Dual Fronts of Digital Defense: Combating Hacking and Fortifying Data Protection///Hacking's New Frontier: Fortifying Data Protection in the Age of Advanced Cyber Threats///The Dual Front: Navigating Hacking Threats and Fortifying Data Protection in the Digital Age///Navigating the Digital Gauntlet: The Evolving Nexus of Hacking and Data Protection///The Unrelenting Cyber Battle: Hacking Threats and the Imperative of Robust Data Protection///Navigating the Cyber Labyrinth: Bolstering Defenses Against Evolving Hacking Threats///The Dual Front War: Battling Hacking and Bolstering Data Protection in the Digital Age///The Ever-Evolving Cyber Threat Landscape: Navigating Hacking and Fortifying Data Protection///The Unseen Battle: Fortifying Data in an Age of Relentless Hacking///The Unseen War: Hacking's Relentless Advance and the Imperative of Data Protection///The Evolving Threat Landscape: Hacking, Data Protection, and the Imperative for Proactive Security///Navigating the Digital Minefield: Bolstering Data Protection in an Era of Relentless Hacking///The Dual Fronts of Digital Defense: Combating Hacking and Fortifying Data Protection///Hacking's New Frontier: Fortifying Data Protection in the Age of Advanced Cyber Threats///The Dual Front: Navigating Hacking Threats and Fortifying Data Protection in the Digital Age///Navigating the Digital Gauntlet: The Evolving Nexus of Hacking and Data Protection///
Subscribe
Cyber Security
Independent · Digital
Thehackingpost
RSSSubscribe
CybersecurityAI-assisted

SUSE Fleet: Plain Text Storage of Vulnerability Exploit Helm Values

## Cybersecurity: Vulnerability in SUSE Fleet

JBy Joseph CainSep 01, 20252 min read

Cybersecurity: Vulnerability in SUSE Fleet

A high-severity vulnerability has been identified in SUSE’s Fleet, a GitOps management tool for Kubernetes clusters. The vulnerability, disclosed by a security researcher via GitHub Security Advisory GHSA-6h9x-9j5v-7w9h, is tracked as CVE-2024-52284 . This issue allows Helm chart values, which may contain sensitive credentials, to be stored in plain text within BundleDeployment resources, making them accessible to users with GET or LIST permissions.

SUSE Fleet facilitates continuous deployment by reconciling Git repositories with Kubernetes manifests. However, when users supply custom Helm values via the BundleDeployment.Spec.Options.Helm.Values field, Fleet directly applies these values in its reconciliation loop without encryption, unlike Helm v3, which secures chart state and values in Kubernetes Secrets.

The vulnerability mainly results in unauthorized disclosure of secrets. Users with permissions to list or retrieve BundleDeployment objects within a cluster can access unencrypted Helm values, exposing sensitive data. This is due to Kubernetes not encrypting custom resource fields at rest by default. The leaked values are vulnerable to compromise by anyone with datastore access to the cluster.

The vulnerability has a CVSS v3.1 base score of 7.4 (High), characterized by:

Attack Vector: Network Attack Complexity: Low Privileges Required: Low User Interaction: None Scope: Changed Confidentiality Impact: High Integrity Impact: None Availability Impact: None

A high-severity vulnerability has been identified in SUSE’s Fleet, a GitOps management tool for Kubernetes clusters.
Joseph Cain · Thehackingpost

=0.11.0, <0.11.10 =0.12.0, <0.12.6 =0.13.0, <0.13.1

Versions 0.14.0, 0.13.1, 0.12.6, and 0.11.10 have the patch. The update ensures that Fleet creates a dedicated Kubernetes Secret for each BundleDeployment’s Helm values, securing these values from exposure.

Immediate mitigation involves upgrading to a patched release. For environments unable to upgrade promptly, users can mitigate exposure by avoiding direct in-spec value files. Instead, reference values files by filename only, ensuring Fleet’s exclusion logic places them into Secrets:

Advertisement

Upgrade Fleet to v0.14.0 or a later patched version. Audit existing BundleDeployments for exposed secrets and rotate any compromised credentials immediately. Enable Kubernetes encryption at rest for critical namespaces to enhance protection. Review RBAC policies to restrict GET and LIST operations on BundleDeployment resources to trusted users.

Addressing this vulnerability not only secures SUSE Fleet deployments but reinforces the principle of not exposing secrets in plain text within cluster manifests.

Based on reporting by GBHackers.

AI transparency. This article was produced with the assistance of artificial intelligence and published under human editorial oversight. AI systems can make mistakes. Read how we use AI (EU AI Act, Art. 50).
Related Stories
Cybersecurity

Why Fintech Banking Platforms Are Reducing Operational Costs by 40%

Paige Monroe · Mar 26, 2026
Cybersecurity

Dogecoin Price Prediction: SHIB Burns 172M Tokens as Pepeto Exchange Earns From Every Trade

Eric Wallace · Mar 26, 2026
Cybersecurity

Solana Price Prediction: SOL Holds $86 With Commodity Status as Pepeto Targets Bigger Returns

Zachary Burns · Mar 26, 2026
Cybersecurity

Open Directory Malware Campaign Uses Obfuscated VBS, PNG Loaders and RAT Payloads

Joseph Cain · Mar 26, 2026