CVE-2025-53547: Helm Code Injection Vulnerability via Malicious Chart.yaml Content
Summary
CVE-2025-53547: Helm vulnerable to Code Injection through malicious chart.yaml content. Affects helm.sh/helm/v3 across 2 version ranges.
< 3.17.4
>= 3.18.0-rc.1, < 3.18.4
Fixed in 3.17.4 or 3.18.4, depending on the release line you run. How to fix ↓
Also tracked for
- helm · Bitnami
The same CVE-2025-53547 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Helm is a package manager for Kubernetes that streamlines the deployment and management of applications on Kubernetes clusters. It allows users to define, install, and upgrade even the most complex Kubernetes applications. Helm uses a packaging format called charts, which contain all the necessary information to create an instance of a Kubernetes application. However, Helm has a vulnerability that can lead to code injection through specially crafted Chart.yaml files.
Vulnerability Detail
A vulnerability exists in Helm where a maliciously crafted Chart.yaml file, when combined with a symlinked Chart.lock file, can lead to local code execution during dependency updates. Specifically, fields in the Chart.yaml can be manipulated to execute code if they are written to a file that is executed, such as a bash.rc file or shell script. This occurs when the helm dependency update command is run, allowing the attacker to exploit the symlink to execute unwanted code. The vulnerability is classified under CWE-94 (Code Injection) and has a CVSS score of 8.5, indicating a high severity.
How To Fix
Latest published version: v3.22.1 as of 22 Oct 2026
go get helm.sh/helm/v3@v3.22.1Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 3.17.43.17.4go get helm.sh/helm/v3@v3.17.4 -
>= 3.18.0-rc.1, < 3.18.43.18.4go get helm.sh/helm/v3@v3.18.4
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, ensure that the Chart.lock file in your chart is not a symlink before updating dependencies. You can check this by running the command: 'ls -l Chart.lock' and verifying that it does not point to another file.
Conclusion
The Helm vulnerability CVE-2025-53547 poses a significant risk due to the potential for code injection through malicious Chart.yaml files. Users are strongly encouraged to update to the patched version 3.18.4 or later to mitigate this risk. Additionally, implementing the provided workaround can help protect against exploitation until an update can be applied.
See every vulnerability recorded for helm.sh/helm/v3 →
FAQ
The vulnerability can lead to local code execution, allowing an attacker to execute arbitrary code on the system where Helm is run.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Helm versions prior to 3.18.4 are affected by this vulnerability.
If you cannot update Helm immediately, ensure that your Chart.lock file is not a symlink before running any dependency updates.
The vulnerability was disclosed by Jakub Ciolek at AlphaSense.
References
Related vulnerabilities
Recent vulnerabilities recorded for helm.sh/helm/v3.
