CVE-2025-53547: Helm vulnerable to Code Injection through malicious chart.yaml content
A Helm contributor discovered that a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated. Impact Fields in a Chart.yaml file, that are carried over to a Chart.lock file when dependencies are updated and this file is written, can be crafted in a way that can cause execution if that same content were in a file that is executed…
Published Jul 8, 2025 · Updated Jul 16, 2025
Affected packages
helm.sh/helm/v3
- Ecosystem
- Go
- Affected
- >= 3.18.0-rc.1, < 3.18.4
- Fixed in
- 3.18.4
- Check
go list -m helm.sh/helm/v3
helm.sh/helm/v3
- Ecosystem
- Go
- Affected
- < 3.17.4
- Fixed in
- 3.17.4
- Check
go list -m helm.sh/helm/v3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A Helm contributor discovered that a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated.
Impact
Fields in a Chart.yaml file, that are carried over to a Chart.lock file when dependencies are updated and this file is written, can be crafted in a way that can cause execution if that same content were in a file that is executed (e.g., a bash.rc file or shell script). If the Chart.lock file is symlinked to one of these files updating dependencies will write the lock file content to the symlinked file. This can lead to unwanted execution. Helm warns of the symlinked file but did not stop execution due to symlinking.
This affects when dependencies are updated. When using the helm command this happens when helm dependency update is run. helm dependency build can write a lock file when one does not exist but this vector requires one to already exist. This affects the Helm SDK when the downloader Manager performs an update.
Patches
This issue has been resolved in Helm v3.18.4
Workarounds
Ensure the Chart.lock file in a chart is not a symlink prior to updating dependencies.
For more information
Helm's security policy is spelled out in detail in our SECURITY document.
Credits
Disclosed by Jakub Ciolek at AlphaSense.
Credited to jake-ciolek.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-35206
Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment
medium4.8Apr 10, 2026CVE-2025-55198
Helm May Panic Due To Incorrect YAML Content
medium6.5Aug 14, 2025CVE-2025-55199
Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion
medium6.5Aug 14, 2025CVE-2025-32386
Helm Allows A Specially Crafted Chart Archive To Cause Out Of Memory Termination
medium6.5Apr 10, 2025CVE-2025-32387
Helm Allows A Specially Crafted JSON Schema To Cause A Stack Overflow
medium6.5Apr 10, 2025CVE-2024-26147
Helm's Missing YAML Content Leads To Panic
high7.5Feb 22, 2024
