Skip to content

Arbitrary command injection via Gradle Wrapper and malicious `distributionUrl`

Moderate
jamietanna published GHSA-pfq2-hh62-7m96 Jan 13, 2026

Package

docker docker.io/mend/renovate-ce (docker)

Affected versions

< 13.3.0

Patched versions

13.3.0
docker docker.io/mend/renovate-ee-server (docker)
< 13.3.0
13.3.0
docker docker.io/mend/renovate-ee-worker (docker)
< 13.3.0
13.3.0
docker docker.io/renovate/renovate (docker)
>=32.124.0 <42.68.5
42.68.5
docker ghcr.io/mend/renovate-ce (docker)
< 13.3.0
13.3.0
docker ghcr.io/mend/renovate-ee-server (docker)
< 13.3.0
13.3.0
docker ghcr.io/mend/renovate-ee-worker (docker)
< 13.3.0
13.3.0
docker ghcr.io/renovate/renovate (docker)
>=32.124.0 <42.68.5
42.68.5
docker mend/renovate-ce (docker)
< 13.3.0
13.3.0
docker mend/renovate-ee-server (docker)
< 13.3.0
13.3.0
docker mend/renovate-ee-worker (docker)
< 13.3.0
13.3.0
npm renovate (npm)
>=32.124.0 <42.68.5
42.68.5
docker renovate/renovate (docker)
>=32.124.0 <42.68.5
42.68.5

Description

Summary

Renovate can be tricked into executing shell code while updating the Gradle Wrapper. A malicious distributionUrl in gradle/wrapper/gradle-wrapper.properties can lead to command execution in the Renovate runtime.

Details

When Renovate handles Gradle Wrapper artifacts, it may run a wrapper update command such as:

  • ./gradlew :wrapper --gradle-distribution-url <value>

In the observed behavior, Renovate executes this via a shell (e.g., /bin/sh -c ...).
If distributionUrl contains shell command substitution syntax like $(...), the shell evaluates it before Gradle validates/parses the URL.

After that, Gradle attempts to parse the URL as a URI and fails with URISyntaxException, but the shell substitution has already executed.

This is reproducible even when allowScripts is disabled (default is OFF), because this execution happens as part of Gradle Wrapper artifact handling rather than “repository install scripts”.

Prerequisites / attack conditions:

  • The attacker must be able to get a malicious gradle-wrapper.properties into a repository that Renovate scans (e.g., direct write access, or a maintainer merges an attacker’s change/PR).
  • Renovate must be configured to process Gradle Wrapper updates/artifacts for that repository (default behavior for the Gradle Wrapper manager).

PoC

  1. Create a repository with a Gradle Wrapper (gradlew, gradlew.bat, gradle/wrapper/gradle-wrapper.jar, and gradle/wrapper/gradle-wrapper.properties).
  2. Set distributionUrl in gradle-wrapper.properties to include $(...).
  3. Run Renovate against the repository.
  4. Observe that a file is created during Renovate’s wrapper update step before Gradle fails with URISyntaxException.

A screen recording is attached showing end-to-end reproduction. In the demo, the payload creates /tmp/passwd_dump containing /etc/passwd, demonstrating that file read/exfiltration is possible within the Renovate execution context.

Impact

This allows arbitrary command execution in the Renovate runtime during Gradle Wrapper updates. Depending on deployment, this may expose credentials/tokens available to the bot and may allow an attacker to modify repositories or access internal resources reachable from the Renovate environment.

Remediation

Upgrading to Renovate 42.68.5 (2025-12-31) fixes this issue, and closes out other risks of shell evaluation for commands run by Renovate.

If using the composer, yarn (v1) or flux managers, please upgrade to 42.74.5 (2026-01-08), as there were follow-up fixes to keep these managers working.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CVE ID

No known CVE

Weaknesses

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Learn more on MITRE.

Credits