# Helm Improper Certificate Validation in helm.sh/helm

Advisory record · `GHSA-x6r5-vxfg-gq3v`

- **Identifiers:** `GHSA-x6r5-vxfg-gq3v` · `CVE-2019-1010275` · `GO-2023-1993`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 20 Aug 2024
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Aug 2024, 20:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `helm.sh/helm` (Go): affected `<2.7.2+incompatible`; fixed in `2.7.2+incompatible`

## Machine-written summary

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

> Helm (helm.sh/helm) versions before 2.7.2+incompatible are affected. The source gives few details beyond the title, which describes improper certificate validation, so the exact conditions and impact are not stated. Upgrade to 2.7.2+incompatible or later.

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

No source has published a CVSS score for this record yet.

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

## Timeline

This record came from the full history of the GitHub Advisory Database, published 20 Aug 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-x6r5-vxfg-gq3v](https://github.com/advisories/GHSA-x6r5-vxfg-gq3v)
- [OSV: GHSA-x6r5-vxfg-gq3v](https://osv.dev/vulnerability/GHSA-x6r5-vxfg-gq3v)
- <https://github.com/advisories/GHSA-x6r5-vxfg-gq3v>
- <https://nvd.nist.gov/vuln/detail/CVE-2019-1010275>
- <https://github.com/helm/helm/commit/1096813bf9a425e2aa4ac755b6c991b626dfab50>
- <https://github.com/helm/helm/pull/3152>
- <https://github.com/helm/helm/pull/3152/files/1096813bf9a425e2aa4ac755b6c991b626dfab50>
- <https://github.com/helm/helm/releases/tag/v2.7.2>

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-x6r5-vxfg-gq3v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x6r5-vxfg-gq3v/>. Everything for agents: <https://agentprime.io/llms.txt>.
