# CVE-2026-35205: Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install

> Helm fails open on missing provenance files, allowing installation of unsigned plugins when signature verification is enabled.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** BIT-helm-2026-35205, CLEANSTART-2026-KS65231, GHSA-q5jf-9vfq-h4h7, GO-2026-5566, MINI-38fw-79v2-jhp9, MINI-45xv-g8vm-36qf, MINI-5vjx-qp6g-5348, MINI-7pw8-52gp-hf5m, MINI-cjrp-38g3-27wg, MINI-pc6q-92xp-mjw4, MINI-qq6g-32x7-jrq8

## What is CVE-2026-35205?

CVE-2026-35205 is a high-severity vulnerability in helm, published on 9 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, Helm will install plugins missing provenance (.prov file) when signature verification is required. This vulnerability is fixed in 4.1.4.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-636 (Not Failing Securely)

## Which versions are affected by CVE-2026-35205?

4 open source packages ship an affected version, including helm.sh/helm/v4 and helm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `helm.sh/helm/v4` | Go | From 4.0.0 | 4.1.4 |
| `helm.sh/helm/v4` | Go | From 4.0.0 | 4.1.4 |
| `helm.sh/helm/v4` | Go | From 4.0.0 | 4.1.4 |
| `helm` | Bitnami | From 4.0.0 | 4.1.4 |

Products: Helm Helm.

## How do I fix CVE-2026-35205?

Upgrade helm.sh/helm/v4 to 4.1.4 or later.

## Is CVE-2026-35205 being exploited?

There is no known exploitation of CVE-2026-35205 in the wild and no public exploit code.

## Other vulnerabilities in helm

- [CVE-2019-18658](https://insights.sbomify.com/CVE-2019-18658/): Helm Unsafe Link Following (critical 9.8)
- [CVE-2019-1010275](https://insights.sbomify.com/CVE-2019-1010275/): Helm Improper Certificate Validation (critical 9.8)
- [CVE-2019-25210](https://insights.sbomify.com/CVE-2019-25210/): Information disclosure in n/a (critical 9.1)
- [CVE-2025-53547](https://insights.sbomify.com/CVE-2025-53547/): Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution (high 8.5)
- [CVE-2020-11013](https://insights.sbomify.com/CVE-2020-11013/): lookup Function Information Discolosure in Helm (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35205 and fix it if it is affected.

What it is: CVE-2026-35205 is a high-severity vulnerability in helm, published on 9 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-35205 in the wild and no public exploit code.

Affected packages and fixed versions:
- helm.sh/helm/v4 (Go): affected from 4.0.0; fixed in 4.1.4
- helm.sh/helm/v4 (Go): affected from 4.0.0; fixed in 4.1.4
- helm.sh/helm/v4 (Go): affected from 4.0.0; fixed in 4.1.4
- helm (Bitnami): affected from 4.0.0; fixed in 4.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35205/ (Markdown: https://insights.sbomify.com/CVE-2026-35205/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35205
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35205
- OSV: https://osv.dev/vulnerability/CVE-2026-35205

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35205/
Summaries are generated and may contain mistakes; the official description above is the record.