Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: helm helm 4.1.4.
Low priority for now. Upgrade to helm helm 4.1.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 9, 2026
- Updated
- Jul 15, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-636
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| helm | helm | cpe:2.3:a:helm:helm |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- helm helm4.0.0 and later · before 4.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
helm helm
- >= 4.0.0, < 4.1.4affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | helm.sh/helm/v4 | from 4.0.0 · before 4.1.4 | 4.1.4 |
| openSUSE:Leap 16.0 | govulncheck-vulndb | before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
| openSUSE:Leap 16.0 | helm | before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
| openSUSE:Tumbleweed | helm | before 4.1.4-2.1 | 4.1.4-2.1 |
| SUSE:Linux Enterprise Server 16.0 | govulncheck-vulndb | before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
| SUSE:Linux Micro 6.2 | helm | before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
Same product
helm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-18658In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a maliciou40Plan
- CVE-2019-1010275helm Before 2.7.2 is affected by: CWE-295: Improper Certificate Validation.39Monitor
- CVE-2025-53547Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-55199Aug 13, 2025 · Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion26Monitor
- ← EarlierCVE-2026-35204Apr 9, 2026 · Helm has a path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory33Monitor
- Later →CVE-2026-35206Apr 9, 2026 · Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| helm helm | 4.1.4 · description | Vendor (CNA) |
| Go:helm.sh/helm/v4 | 4.1.4 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20260727T201416-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:helm | 4.1.4-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20260727T201416-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:helm | 4.3.0-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-636 · Not Failing Securely ('Failing Open')CVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/helm/helm/releases/tag/v4.1.4
- github.com/helm/helm/security/advisories/GHSA-q5jf-9vfq-h4h7
- helm.sh/docs/topics/provenance/#the-provenance-file
- access.redhat.com/errata/RHSA-2026:26441
- access.redhat.com/security/cve/CVE-2026-35205
- bugzilla.redhat.com/show_bug.cgi?id=2456927
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35205.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.