# Helm Chart extraction output directory collapse via \`Chart.yaml\` name dot-segment

Advisory record · `GHSA-hr2v-4r36-88hr`

- **Identifiers:** `GHSA-hr2v-4r36-88hr` · `BIT-helm-2026-35206` · `CVE-2026-35206` · `GO-2026-5435`
- **State:** Confirmed
- **Severity:** CVSS 4.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 10 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Apr 2026, 15:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `helm.sh/helm/v4` (Go): affected `<4.1.4`; fixed in `4.1.4`
- `helm.sh/helm/v3` (Go): affected `<3.20.2`; fixed in `3.20.2`

## Machine-written summary

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

> Helm (Go modules helm.sh/helm/v4 before 4.1.4 and helm.sh/helm/v3 before 3.20.2) can extract a crafted Chart's contents directly into the output directory instead of a subdirectory named after the chart, when the chart name is a dot segment. An attacker who supplies a malicious chart to a user running "helm pull --untar" could cause existing files in the output directory to be overwritten. Upgrade to helm.sh/helm/v4 4.1.4 or helm.sh/helm/v3 3.20.2. Until then, use an empty or dedicated output directory for untarring.

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

- 4.8 Medium, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

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

## Timeline

- 9 Apr 2026, 21:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-35206)
- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hr2v-4r36-88hr)

## Sources

- [GitHub Advisory Database: GHSA-hr2v-4r36-88hr](https://github.com/advisories/GHSA-hr2v-4r36-88hr)
- [OSV: GHSA-hr2v-4r36-88hr](https://osv.dev/vulnerability/GHSA-hr2v-4r36-88hr)
- <https://github.com/helm/helm/security/advisories/GHSA-hr2v-4r36-88hr>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-35206>
- <https://github.com/helm/helm/commit/4e7994d4467182f535b6797c94b5b0e994a91436>
- <https://github.com/helm/helm>
- <https://github.com/helm/helm/releases/tag/v4.1.4>

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-hr2v-4r36-88hr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hr2v-4r36-88hr/>. Everything for agents: <https://agentprime.io/llms.txt>.
