CVE-2026-35205 affects Helm, the Kubernetes package manager for Charts. In Helm versions 4.0.0 through 4.1.3, plugin installation logic will install plugins even when the expected provenance (.prov) file is missing, despite signature verification being required. This results in a failure to properly enforce provenance verification during plugin installation, allowing installation to proceed without the required signed provenance artifact. The issue undermines the trust model for verified plugin installation. The vulnerability is fixed in Helm 4.1.4.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Insufficient verification of Helm plugin provenance can permit arbitrary code execution. This vulnerability is the source of the reference's CVSS v2 base score of 7.2.
A vulnerability in Helm where versions 4.0.0 through 4.1.3 may install plugins missing a provenance (.prov) file even when signature verification is required.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.