Code execution via symlinked dependency lock overwrite
Published Jul 8, 2025 · Updated Feb 26, 2026
Code injection in Helm through 3.17.3 and 3.18.0 through 3.18.3 allows attackers to execute code via a malicious chart. pkg/downloader writeLock follows an existing Chart.lock symlink and writes fields copied from untrusted Chart.yaml content into its target. Exploitation requires a user or consuming SDK to update the chart's dependencies and later execute the overwritten shell script or startup file.
Summary
What happened
Code injection in Helm through 3.17.3 and 3.18.0 through 3.18.3 allows attackers to execute code via a malicious chart. pkg/downloader writeLock follows an existing Chart.lock symlink and writes fields copied from untrusted Chart.yaml content into its target. Exploitation requires a user or consuming SDK to update the chart's dependencies and later execute the overwritten shell script or startup file.
The record
- CVE
- CVE-2025-53547
- Published
- Jul 8, 2025
- Updated
- Feb 26, 2026
- Vendor
- The Helm Project
- Product
- Helm
- Classifications
- CWE-94, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.18.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo