# Helm vulnerable to Code Injection through malicious chart.yaml content

Advisory record · `GHSA-557j-xg8c-q2mm`

- **Identifiers:** `GHSA-557j-xg8c-q2mm` · `BIT-helm-2025-53547` · `CVE-2025-53547` · `GO-2025-3802`
- **State:** Confirmed
- **Severity:** CVSS 8.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 8 Jul 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Jul 2025, 23:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `helm.sh/helm/v3` (Go): affected `>=3.18.0-rc.1, <3.18.4 || <3.17.4`; fixed in `3.18.4`, `3.17.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Helm (helm.sh/helm/v3) versions before 3.17.4 and from 3.18.0-rc.1 before 3.18.4 are vulnerable. An attacker who supplies a crafted Chart.yaml and a symlinked Chart.lock can cause Helm to write attacker-controlled content into a file that is later executed, such as a shell rc file, when dependencies are updated. Upgrade to Helm 3.17.4 or 3.18.4. As a workaround, make sure Chart.lock is not a symlink before running dependency updates.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.5 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0053, the 45th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 8 Jul 2025, 20:50 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/helm/helm/security/advisories/GHSA-557j-xg8c-q2mm)
- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-557j-xg8c-q2mm)

## Sources

- [GitHub Advisory Database: GHSA-557j-xg8c-q2mm](https://github.com/advisories/GHSA-557j-xg8c-q2mm)
- [OSV: GHSA-557j-xg8c-q2mm](https://osv.dev/vulnerability/GHSA-557j-xg8c-q2mm)
- <https://github.com/helm/helm/security/advisories/GHSA-557j-xg8c-q2mm>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-53547>
- <https://github.com/helm/helm/commit/4b8e61093d8f579f1165cdc6bd4b43fa5455f571>
- <https://github.com/helm/helm>
- <https://news.ycombinator.com/item?id=44506696>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-557j-xg8c-q2mm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-557j-xg8c-q2mm/>. Everything for agents: <https://agentprime.io/llms.txt>.
