Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin installGHSA-q5jf-9vfq-h4h7
HIGHFix: helm/helm@05fa379GHSA-q5jf-9vfq-h4h7 is a high-severity (CVSS 7.8) CWE-636 vulnerability in helm.sh/helm/v4. A fix is available for helm.sh/helm/v4 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-q5jf-9vfq-h4h7.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
helm.sh/helm/v4Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Helm 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | helm.sh/helm/v4 | ≥ 4.0.0&&< 4.1.4 | 4.1.4go get helm.sh/helm/v4@v4.1.4 |
Affected Products
helmhelmDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for helm.sh/helm/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update helm.sh/helm/v4 to 4.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q5jf-9vfq-h4h7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-q5jf-9vfq-h4h7 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Helm CLI 4.1 | helm-cli-4.1.4 | RHSA-2026:26441 |
Frequently Asked Questions
Is GHSA-q5jf-9vfq-h4h7 in your dependencies?
Find it across Go, including transitive dependencies.