GHSA-xv56-3wq5-9997: Renovate vulnerable to arbitrary command injection via kustomize manager and malicious helm repository
Summary The user-provided chart name in the kustomize manager is appended to the helm pull --untar command without proper sanitization. Details Adversaries can provide a maliciously crafted kustomization.yaml in conjunction with a Helm repo's index.yaml file to trick Renovate to execute arbitrary code.
Published Jan 13, 2026
Affected packages
renovate
- Ecosystem
- npm
- Affected
- >= 39.218.0, < 40.33.0
- Fixed in
- 40.33.0
- Check
npm ls renovate
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The user-provided chart name in the kustomize manager is appended to the helm pull --untar command without proper sanitization.
Details
Adversaries can provide a maliciously crafted kustomization.yaml in conjunction with a Helm repo's index.yaml file to trick Renovate to execute arbitrary code. The value for the depName argument for the helmRepositoryArgs function in lib/modules/manager/kustomize/artifacts.ts is not being escaped using the quote function from the shlex package. This lack of proper sanitization has been present in the product since version 39.218.9 (https://github.com/renovatebot/renovate/commit/cc08c6e98f19e6258c5d3180c70c98e1be0b0d37), released on March 26 of 2025.
PoC
- Create a mock Helm repository. Have its
index.yamlendpoint return:
apiVersion: v1
entries:
"example || kill 1; echo":
- version: 1.0.1
created: 2016-10-06T16:23:20.499814565-06:00
- version: 1.0.0
created: 2016-10-06T16:23:20.499543808-06:00- Create a git repo with the following content:
renovate.json5:
{
$schema: "https://docs.renovatebot.com/renovate-schema.json",
postUpdateOptions: [
"kustomizeInflateHelmCharts",
]
}kustomization.yaml:
kind: Kustomization
apiVersion: kustomize.config.k8s.io/v1beta1
helmCharts:
- name: "example || kill 1; echo"
repo: TODO reference the mocked Helm repository over https
version: 1.0.0with the todo resolved
charts/.gitkeep:
(empty)
- Run Renovate against the repo from a Docker container. Notice that the process terminates without reporting "Repository finished", because the ACI vulnerability allowed for execution of
kill 1, terminating the root process of the container.
Impact
This is a Arbitrary Command Injection vulnerability, allowing those with write access on repositories configured to be scanned by Renovate to cause the execution of commands of their choice on the machine that runs Renovate.
Credited to astellingwerf.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesGHSA-5vjq-5jmg-39xq
Renovate affected by remote code execution was possible using the bazel-module or bazelisk managers, when using lockFileMaintenance
medium6.3Apr 16, 2026GHSA-8wc6-vgrq-x6cf
Child processes spawned by Renovate incorrectly have full access to environment variables
medium5.5Feb 13, 2026GHSA-36j9-mx87-2cff
Renovate vulnerable to arbitrary command injection via hermit manager and maliciously named dependencies
medium6.7Jan 13, 2026GHSA-3f44-xw83-3pmg
Renovate vulnerable to arbitrary command injection via helmv3 manager and malicious Chart.yaml file
medium6.7Jan 13, 2026GHSA-fr4j-65pv-gjjj
Renovate vulnerable to arbitrary command injection via npm manager and malicious Renovate configuration
medium6.7Jan 13, 2026GHSA-pfq2-hh62-7m96
Renovate vulnerable to arbitrary command injection via Gradle Wrapper and malicious `distributionUrl`
medium6.7Jan 13, 2026
