Helm hat eine Pfadüberschreitung in Plugin-Metadaten, die das Schreiben beliebiger Dateien außerhalb des Helm-Plugin-Verzeichnisses ermöglicht

The core impact of CVE-2026-35204 lies in the ability of a malicious Helm plugin to bypass intended file system boundaries. An attacker could craft a plugin that, upon installation or update, attempts to write its contents to a location outside of the designated plugin directory. This could lead to the overwriting of critical system files, configuration files, or even user data. The potential for data loss, system instability, and further compromise is significant. This vulnerability shares similarities with other file system traversal exploits, where attackers leverage vulnerabilities to access or modify files beyond their intended scope.

Organizations heavily reliant on Helm for managing Kubernetes deployments are at risk. This includes DevOps teams, platform engineers, and anyone responsible for maintaining Kubernetes clusters. Users who have installed plugins from untrusted sources are particularly vulnerable. Shared hosting environments where multiple users share a single Helm installation are also at increased risk.

• linux / server: Monitor Helm plugin directories (e.g., /var/lib/helm/plugins) for unexpected files or modifications. Use ls -l and find commands to identify anomalies.

find /var/lib/helm/plugins -type f -mmin -60 -print

• go: Inspect Helm plugin code for suspicious file path manipulation. Look for functions like os.MkdirAll or os.Create used with user-controlled input. • generic web: Examine Helm logs for errors related to file writing or permission denied errors.

journalctl -u helm -f

1. 2026-04-10Disclosure

   disclosure

1. Reserviert2026-04-01
2. Veröffentlicht2026-04-10
3. Geändert2026-04-13
4. EPSS aktualisiert2026-04-17

The primary mitigation for CVE-2026-35204 is to upgrade Helm to version 4.1.4 or later, which includes the necessary fix. If upgrading is not immediately feasible, consider implementing stricter plugin source validation. Only install plugins from trusted repositories and carefully review the plugin's code before installation. As a more restrictive workaround, consider running Helm in an environment with a read-only filesystem, limiting the potential damage from a malicious plugin. Monitor Helm logs for unusual file access patterns or attempts to write to unexpected locations.