# Helm passes repository credentials to alternate domain

Advisory record · `GHSA-56hp-xqp3-w2jf`

- **Identifiers:** `GHSA-56hp-xqp3-w2jf` · `BIT-helm-2021-32690` · `CVE-2021-32690` · `GHSA-7jr6-prv4-5wf5` · `GO-2022-0384`
- **State:** Confirmed
- **Severity:** CVSS 6.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 23 Jun 2021
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Jun 2021, 18:14 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.6.1`; fixed in `3.6.1`

## 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.6.1 passed a Helm repository's username and password to other domains referenced in that repository's index.yaml when retrieving chart archives. An attacker controlling or influencing a chart repository's index could receive those credentials, which requires the repository to use credentials. Upgrade to Helm 3.6.1 or later, which scopes credentials to the repository's scheme, host, and port; the --pass-credentials flag restores the old behavior when needed.

Written 6 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

- 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 73rd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:44 UTC: First seen by agentprime
- 31 Oct 2026, 14:44 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-56hp-xqp3-w2jf)

## Sources

- [GitHub Advisory Database: GHSA-56hp-xqp3-w2jf](https://github.com/advisories/GHSA-56hp-xqp3-w2jf)
- [OSV: GHSA-56hp-xqp3-w2jf](https://osv.dev/vulnerability/GHSA-56hp-xqp3-w2jf)
- <https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf>
- <https://nvd.nist.gov/vuln/detail/CVE-2021-32690>
- <https://github.com/helm/helm/commit/61d8e8c4a6f95540c15c6a65f36a6dd0a45e7a2f>
- <https://github.com/helm/helm>
- <https://github.com/helm/helm/releases/tag/v3.6.1>
- <https://pkg.go.dev/vuln/GO-2022-0384>

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-56hp-xqp3-w2jf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-56hp-xqp3-w2jf/>. Everything for agents: <https://agentprime.io/llms.txt>.
