CVE-2026-35204
HighCVSS 8.6Exploitation Probability (EPSS)
Low risk5th percentile - higher than 5% of all known CVEs
Summary
A vulnerability in Helm from version 4.0.0 to 4.1.3 allows writing plugin contents to arbitrary filesystem locations via a crafted 'version' field in plugin.yaml containing '/../' (dot-dot) path separators.
Risk Assessment
An attacker could exploit this to overwrite critical system or configuration files, potentially leading to privilege escalation or full cluster compromise.
Recommendation
Upgrade Helm to version 4.1.4 or later immediately, and validate that plugin.yaml files do not contain relative path separators before installing plugins.
Other vulnerabilities in Helm
See all- CVE-2026-66016Medium
Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.
- CVE-2026-63308Medium
A denial of service vulnerability in Helm through version 4.2.3 (fixed in commit ba6c9a2) causes an index out of range panic in the Files.Lines template helper in pkg/engine/files.go. Attackers can include empty files in Helm charts, leading to deterministic render failures during template, install, upgrade, lint, and SDK Engine.Render operations.
- CVE-2026-35205High
Helm versions 4.0.0 through 4.1.3 install plugins missing provenance (.prov file) when signature verification is required. This vulnerability is fixed in version 4.1.4.
Original NVD description (English source)
Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, a specially crafted Helm plugin, when installed or updated, will cause Helm to write the contents of the plugin to an arbitrary filesystem location. To prevent this, validate that the plugin.yaml of the Helm plugin does not include a version: field containing POSIX dot-dot path separators ie. "/../". This vulnerability is fixed in 4.1.4.