Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-35205 high CVSS 7.8

Vulnerability in helm.sh/helm/v4 (CVE-2026-35205)

Summary

Vulnerability in helm.sh/helm/v4 (CVE-2026-35205). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.1.4 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-35205 has been found in helm.sh/helm/v4.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade helm.sh/helm/v4 to 4.1.4 or later.
If unsure, ask your IT team or search "helm.sh/helm/v4 CVE-2026-35205" on the vendor's site.

CVE-2026-35205 (helm.sh/helm/v4) — CWE-636 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 4.1.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-636) exists in helm.sh/helm/v4.

📍 Affected scope

Check the vendor advisory for the affected versions of helm.sh/helm/v4.

🔥 Severity

Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.1.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'helm.sh/helm/v4' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'helm.sh/helm/v4' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で helm.sh/helm/v4 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade helm.sh/helm/v4 to 4.1.4

    ステージング環境で 4.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go helm.sh/helm/v4
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.1.4"}]}]
Bitnami helm
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.1.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details