Loading vulnerability…
CVE-2025-53547 is an improper link-resolution vulnerability in Helm dependency-update handling before version 3.18.4. Attacker-controlled fields from a chart manifest are propagated into the chart's dependency lock data during dependency updates. If the dependency lock file is replaced with a symbolic link to an executable or subsequently interpreted local file, Helm follows the link and overwrites the target with attacker-controlled content. Helm emitted a symlink warning but did not abort the operation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) exploit for CVE-2025-53547, targeting Helm versions 3.18.3 and earlier. The exploit demonstrates a command injection vulnerability in the Helm chart dependency resolution process. By crafting a malicious Chart.yaml with a dependency repository URL containing shell metacharacters, and using a symlinked Chart.lock file (e.g., pointing to /tmp/1.txt), an attacker can inject arbitrary shell commands. The POC shows how this can be used to create a file (/tmp/2.txt) on the target system, but the README notes that any shell command could be executed, including modifying startup scripts for persistence. The repository contains three files: Chart.lock (symlink or file for command injection), Chart.yaml (malicious chart definition), and README.md (usage instructions and explanation). The attack vector is local, requiring the attacker to supply or modify a Helm chart processed by a vulnerable Helm installation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.