Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install
cve-program · CVE-2026-35205
PublishedHelm 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.
Read the publisher's advisoryeuvd · EUVD-2026-20901
PublishedHelm 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.
Read the publisher's advisorynvd · CVE-2026-35205
PublishedHelm 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.
Read the publisher's advisoryosv · GHSA-q5jf-9vfq-h4h7
PublishedHelm is a package manager for Charts for Kubernetes. In Helm versions >=4.0.0 and <=4.1.3, Helm will install plugins missing provenance (`.prov` file) when signature verification is required. ### Impact The bug allows plugin authors to omit provenance (signing) data from plugins, bypassing plugin signature verification upon plugin install/update. Notably, plugin hooks will be executed as designed on the installed plugin, enabling a malicious plugin to execute arbitrary code. ### Patches This issue has been patched in Helm v4.1.4 Installing/updating a plugin with missing provenance will error if signature verification is required. ### Workarounds Users may manually validate that a plugin archive is not missing provenance data (`.prov` file) before installation.
Read the publisher's advisoryosv · GO-2026-5566
PublishedHelm's plugin verification fails open when .prov is missing, allowing unsigned plugin install in helm.sh/helm
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-35205 · CVE overview and exploitation status
cve-program · CVE-2026-35205
- https://github.com/helm/helm/security/advisories/GHSA-q5jf-9vfq-h4h7
- https://github.com/helm/helm/commit/05fa37973dc9e42b76e1d2883494c87174b6074f
- https://github.com/helm/helm/releases/tag/v4.1.4
- https://helm.sh/docs/topics/provenance/#the-provenance-file
euvd · EUVD-2026-20901
- https://github.com/helm/helm/security/advisories/GHSA-q5jf-9vfq-h4h7
- https://github.com/helm/helm/commit/05fa37973dc9e42b76e1d2883494c87174b6074f
- https://github.com/helm/helm/releases/tag/v4.1.4
- https://helm.sh/docs/topics/provenance/#the-provenance-file
nvd · CVE-2026-35205
- https://github.com/helm/helm/commit/05fa37973dc9e42b76e1d2883494c87174b6074f
- https://github.com/helm/helm/releases/tag/v4.1.4
- https://github.com/helm/helm/security/advisories/GHSA-q5jf-9vfq-h4h7
- https://helm.sh/docs/topics/provenance/#the-provenance-file
- https://access.redhat.com/errata/RHSA-2026:26441
- https://access.redhat.com/security/cve/CVE-2026-35205
- https://bugzilla.redhat.com/show_bug.cgi?id=2456927
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35205.json
osv · GHSA-q5jf-9vfq-h4h7
- https://github.com/helm/helm/security/advisories/GHSA-q5jf-9vfq-h4h7
- https://nvd.nist.gov/vuln/detail/CVE-2026-35205
- https://github.com/helm/helm/commit/05fa37973dc9e42b76e1d2883494c87174b6074f
- https://github.com/helm/helm
- https://github.com/helm/helm/releases/tag/v4.1.4
- https://helm.sh/docs/topics/provenance/#the-provenance-file