CVE-2026-35205

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

April 9, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
Patch available. Sources: github_commit, github_release, github.
generic

Helm Provenance and Integrity | Helm

https://helm.sh/docs/topics/provenance/#the-provenance-file
github Patch Available

Plugin verification fails open when `.prov` is missing, allowing unsigned plugin install · Advisory · helm/helm · GitHub

https://github.com/helm/helm/security/advisories/GHSA-q5jf-9vfq-h4h7
github_release Patch Available

Helm v4.1.4

Patch available: helm/helm v4.1.4

https://github.com/helm/helm/releases/tag/v4.1.4
github_commit

commit 05fa37973dc9 (helm/helm)

Fix landed in helm/helm commit 05fa37973dc9 — awaiting tagged release

https://github.com/helm/helm/commit/05fa37973dc9e42b76e1d2883494c87174b6074f

Vendor Advisories for CVE-2026-35205(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathelm-cli-4.1.42026-06-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
helm.sh/helm/v4—4.1.4—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-02 07:44 UTCOSV refresh
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 07:13 UTCEG score recompute
  4. 2026-08-16 07:13 UTCVendor advisory
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 18:24 UTCVendor advisory
  8. 2026-08-14 05:09 UTCEG score recompute
  9. 2026-08-14 05:09 UTCVendor advisory
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 09:25 UTCVendor advisory
  12. 2026-08-12 19:25 UTCEG score recompute
  13. 2026-08-12 19:25 UTCVendor advisory
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 19:29 UTCEG score recompute
  16. 2026-08-11 19:29 UTCVendor advisory
  17. 2026-08-11 03:02 UTCEG score recompute
  18. 2026-08-11 03:02 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 06:50 UTCVendor advisory
  21. 2026-08-09 17:43 UTCEG score recompute
  22. 2026-08-09 17:43 UTCVendor advisory
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 04:35 UTCEG score recompute
  25. 2026-08-09 04:35 UTCVendor advisory
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 03:37 UTCEG score recompute
  28. 2026-08-08 03:37 UTCVendor advisory
  29. 2026-08-07 14:30 UTCEG score recompute
  30. 2026-08-07 14:30 UTCVendor advisory
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 12:52 UTCVendor advisory
  33. 2026-08-05 23:46 UTCEG score recompute
  34. 2026-08-05 23:46 UTCVendor advisory
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-03 22:00 UTCEG score recompute
  39. 2026-08-03 22:00 UTCVendor advisory
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 13:56 UTCEG score recompute
  42. 2026-08-02 13:56 UTCVendor advisory
  43. 2026-08-02 02:27 UTCEPSS rescore
  44. 2026-08-01 04:16 UTCEPSS rescore
  45. 2026-07-30 16:28 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-27 14:13 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-25 14:18 UTCEPSS rescore
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-24 14:17 UTCEPSS rescore
  53. 2026-07-24 14:17 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 03:10 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescore
  58. 2026-07-21 15:24 UTCEPSS rescore
  59. 2026-07-20 20:32 UTCOSV refresh
  60. 2026-07-20 17:08 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 02:29 UTCEPSS rescore
  63. 2026-07-18 10:04 UTCEPSS rescore
  64. 2026-07-16 17:03 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 16:57 UTCEPSS rescore
  67. 2026-07-15 02:23 UTCNVD updateCVSS v3 → 7.8
  68. 2026-07-15 02:00 UTCEPSS rescore
  69. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 8
  70. 2026-07-13 22:30 UTCEPSS rescore
  71. 2026-07-13 06:13 UTCEPSS rescore
  72. 2026-07-13 06:13 UTCEPSS rescore
  73. 2026-07-12 05:46 UTCEPSS rescore
  74. 2026-07-11 08:27 UTCEPSS rescore
  75. 2026-07-09 19:10 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-35205?
CVE-2026-35205 is a high vulnerability published on April 9, 2026. 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.
When was CVE-2026-35205 disclosed?
CVE-2026-35205 was first published in the National Vulnerability Database on April 9, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35205 actively exploited?
CVE-2026-35205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.4% of all scored CVEs.
What is the CVSS score of CVE-2026-35205?
CVE-2026-35205 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-35205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35205, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35205

Explore →

Is Your Infrastructure Affected by CVE-2026-35205?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs