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.
euvd · EUVD-2026-20901 · Published
No access to your tenant or devices. Every item links to its source. What this means
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.
Read the publisher's advisoryHelm 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 advisoryHelm 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 advisoryHelm 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 advisoryHelm's plugin verification fails open when .prov is missing, allowing unsigned plugin install in helm.sh/helm
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
euvd · EUVD-2026-20901 · Published
nvd · CVE-2026-35205 · Published
osv · GHSA-q5jf-9vfq-h4h7 · Published
osv · GO-2026-5566 · Published
cve-program · CVE-2026-35205 · Published