Skip to main content

Improper Control of Generation of Code ('Code Injection') in github.com/helm/helm

CVE-2025-53547

  • github.com/helm/helm
  • github.com/helm/helm/v3
  • github.com/helm/helm/v4
  • helm/helm
  • helm.sh/helm
  • helm.sh/helm/v3
  • helm.sh/helm/v4
  • helm.sh/helm/v3/v3
  • k8s.io/Helm
  • k8s.io/helm/v3
High
8.6/10

Summary

Helm is a package manager for Charts for Kubernetes. In helm.sh/helm/v3 package versions prior to 3.18.4, a specially crafted `Chart.yaml` file along with a specially linked `Chart.lock` file can lead to local code execution when dependencies are updated. Fields in a `Chart.yaml` file, that are carried over to a `Chart.lock` file when dependencies are updated and this file is written, can be crafted in a way that can cause execution if that same content were in a file that is executed (e.g., a `bash.rc` file or shell script). If the `Chart.lock` file is symlinked to one of these files, updating dependencies will write the lock file content to the symlinked file. This can lead to unwanted execution. Helm warns of the symlinked file but did not stop execution due to symlinking.

  • LOW
  • LOCAL
  • HIGH
  • CHANGED
  • REQUIRED
  • NONE
  • HIGH
  • HIGH

CWE-94 - Code Injection

Code injection is a type of vulnerability that allows an attacker to execute arbitrary code. This vulnerability fully compromises the machine and can cause a wide variety of security issues, such as unauthorized access to sensitive information, manipulation of data, denial of service attacks etc. Code injection is different from command injection in the fact that it is limited by the functionality of the injected language (e.g. PHP), as opposed to command injection, which leverages existing code to execute commands, usually within the context of a shell.

References

Advisory Timeline

  • Published