Is CVE-2026-35205 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35205 being exploited in the wild.

How severe is CVE-2026-35205?

High severity, with a CVSS score of 7.8, published 9 April 2026.

Which products and versions are affected?

helm.sh/helm/v4 (Go) >= 4.0.0, = 4.0.0, < 4.1.4.

Is there a fix for CVE-2026-35205?

Yes. helm.sh/helm/v4 (Go): upgrade to 4.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35205 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-35205?

Check whether you run helm.sh/helm/v4 (Go) or Helm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35205: Helm signature verification bypass for plugins missing provenance files

Q: Is there a fix for CVE-2026-35205?

Yes. helm.sh/helm/v4 (Go): upgrade to 4.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-35205 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-35205?

Check whether you run helm.sh/helm/v4 (Go) or Helm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35205 · Severity: high · CVSS 7.8 · Published 2026-04-09

Helm, a popular package manager for Kubernetes, contains a security flaw where it fails to properly verify the digital signatures of plugins. If a user is tricked into installing a malicious plugin that is missing its security verification file, Helm will proceed with the installation even when signature verification is required. This could allow an attacker to execute unauthorized code on the user's system through plugin hooks.

Technologies: helm.sh/helm/v4 (Go), Helm. Vendors: Go, Helm.

Quick answers

Is CVE-2026-35205 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35205 being exploited in the wild.
How severe is CVE-2026-35205?: High severity, with a CVSS score of 7.8, published 9 April 2026.
Which products and versions are affected?: helm.sh/helm/v4 (Go) >= 4.0.0, <= 4.1.3, SEMVER:introduced=4.0.0,fixed=4.1.4; Helm >= 4.0.0, < 4.1.4.
Is there a fix for CVE-2026-35205?: Yes. helm.sh/helm/v4 (Go): upgrade to 4.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35205 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-35205?: Check whether you run helm.sh/helm/v4 (Go) or Helm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

helm.sh/helm/v4 (Go): upgrade to 4.1.4 or later
```
go get helm.sh/helm/v4@v4.1.4
```

Technical details

A 'fail-open' vulnerability exists in Helm's plugin installer (internal/plugin/installer/installer.go) for versions 4.0.0 through 4.1.3. When signature verification is explicitly required during a plugin installation or update, Helm fails to error out if the provenance (.prov) file is entirely absent. An attacker can exploit this by providing a malicious plugin archive without a provenance file, bypassing the cryptographic integrity checks. If a user installs such a plugin, malicious plugin hooks can execute arbitrary code with the privileges of the Helm process. The issue is resolved in version 4.1.4 by ensuring the installer returns an error when provenance data is missing during a verified install.

Affected products

Helm Helm >= 4.0.0, < 4.1.4

Identifiers

CVE-2026-35205
GHSA-q5jf-9vfq-h4h7
GO-2026-5566

Timeline

2026-04-09: disclosed
2026-04-09: patched: Fixed in version 4.1.4
2026-04-09: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.