Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q5jf-9vfq-h4h7

Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install

CVSS 8.4 HighEPSS 0.0022 · 12th percentile

Published by the GitHub Advisory Database at 10 Apr 2026, 15:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
helm.sh/helm/v4Go>=4.0.0, <4.1.44.1.4
Identifiers
GHSA-q5jf-9vfq-h4h7 · BIT-helm-2026-35205 · CVE-2026-35205 · GO-2026-5566
Weakness (CWE)
CWE-347 · CWE-636
Tags
Published
10 Apr 2026
Updated
10 Sept 2026

Machine-written summary

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

Helm (helm.sh/helm/v4) versions >=4.0.0 and <4.1.4 install plugins that lack a provenance (.prov) file even when signature verification is required. An attacker who can publish a plugin can omit signing data to bypass verification, and the plugin's hooks will then run on install or update, allowing arbitrary code execution. Upgrade to Helm 4.1.4, which errors on missing provenance when verification is required. Until then, manually check that a plugin archive includes its provenance file before installing it.

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

ScoreRatingCVSSVectorSource
8.4 High 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

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.