Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
11 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
When using lockFileMaintenance using the bazel-module or bazelisk managers between Renovate 43.65.0 (2026-03-12) and 43.102.11 (2026-04-02), there was the opportunity for remote code execution from a malicious dependency, if the Bazel module executes code that relies on a dependency. As this is an "unsafe" execution path, we have disabled this by default, and self-hosted administrators must add it to the allowedUnsafeExecutions allowlist. It is recommended to review whether you have enabled this functionality for these managers, and if so, whether any dependency updates may have led to remote code execution. Impact If Renovate suggested an update to a malicious dependency, and that dependency is referenced as part of the bazel mod deps call - for instance as part of a ctx.execute call - this would call attacker-controlled code. This could lead to insider attackers and outside attackers, executing code that is distributed as part of the package. Patches This is patched in 43.102.11.…
Recommended action: Upgrade to 43.102.11 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When Renovate spawns child processes, their access to environment variables is filtered to an allowlist, to prevent unauthorized access to privileged credentials that the Renovate process has access to. Since 42.68.1 (2025-12-30), this filtering had been inadvertently removed, and so any child processes spawned from these versions will have had access to any environment variables that Renovate has access to. This could lead to insider attackers and outside attackers being able to exflitrate secrets from the Renovate deployment. It is recommended to rotate (+ revoke) any credentials that Renovate has access to, in case any spawned child processes have attempted to exfiltrate any secrets. Impact Child processes spawned by Renovate (i.e. npm install, anything defined in postUpgradeTasks or postUpdateOptions) will have full access to the environment variables that the Renovate process has. This could lead to insider attackers and outside attackers being able to exflitrate secrets from…
Recommended action: Upgrade to 43.4.4 or 42.96.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The user-provided string repository in the helmv3 manager is appended to the helm registry login command without proper sanitization. Details Adversaries can provide a maliciously crafted Chart.yaml in conjunctions with a tweaked Renovate configuration file to trick Renovate to execute arbitrary code. The value for both uses of the repository variable in lib/modules/manager/helmv3/common.ts are not being escaped using the quote function from the shlex package. This lack of proper sanitization has been present in the product since version 31.51.0 (https://github.com/renovatebot/renovate/commit/f372a68144a4d78c9f7f418168e4efe03336a432), released on January 24 of 2022. PoC 1. Create a git repo with the following content: renovate.json5: Chart.yaml: Chart.lock: 2. 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…
Recommended action: Upgrade to 40.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The user-provided string depName in the gleam manager is appended to the gleam deps update command without proper sanitization. Details Adversaries can provide a maliciously crafted gleam.toml in conjunctions with a tweaked Renovate configuration file to trick Renovate to execute arbitrary code. All values added to the packagesToUpdate variable in lib/modules/manager/gleam/artifacts.ts are 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.53.0 (https://github.com/renovatebot/renovate/commit/d29698e0131231652970f02765312769975e4d38), released on December 6 of 2024. PoC 1. Create a git repo with the following content: renovate.json5: gleam.toml: manifest.toml: 2. 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…
Recommended action: Upgrade to 40.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The user-provided string depName in the hermit manager is appended to the ./hermit install and ./hermit uninstall commands without proper sanitization. Details Adversaries can provide a maliciously named hermit dependency in conjunctions with a tweaked Renovate configuration file to trick Renovate to execute arbitrary code. All values added to the packagesToInstall and packagesToUninstall variables in lib/modules/manager/hermit/artifacts.ts are not being escaped using the quote function from the shlex package. This lack of proper sanitization for installing packages has been present in the product since the introduction of the hermit manager in version 32.135.0 (https://github.com/renovatebot/renovate/commit/b696abb3c2741508fbb4029f39153140a3722e1e), released on July 30 of 2022. In version 37.199.1 (https://github.com/renovatebot/renovate/commit/eaec10d7c8afadbdd783ac47bd2adbfab444d6df) some use of the quote function from the shlex package was added, but not in a way that…
Recommended action: Upgrade to 40.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The user-provided string packageName in the npm manager is appended to the npm install command during lock maintenance without proper sanitization. Details Adversaries can provide a maliciously crafted Renovate configuration file to trick Renovate to execute arbitrary code. The user-provided workspace names and package keys that are added to the updateCmd variables in lib/modules/manager/npm/post-update/npm.ts are not being escaped using the quote function from the shlex package. This lack of proper sanitization has been present in the product since version 35.63.0 (https://github.com/renovatebot/renovate/commit/012c0ac2fe32832e60a62bde405c0a241efd314c), released on April 27 of 2023. PoC 1. Create a git repo with the following content: renovate.json5: package.json: package-lock.json: 2. 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…
Recommended action: Upgrade to 40.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 1. Create a mock Helm repository. Have its index.yaml endpoint return: 2. Create a git repo with the following content: renovate.json5: kustomization.yaml: with the todo resolved charts/.gitkeep: (empty) 3. Run Renovate against the repo from a Docker container. Notice that the process…
Recommended action: Upgrade to 40.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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…
Recommended action: Upgrade to 42.68.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Attackers with commit access to the default branch of a repo using Renovate could manipulate helmv3 registryAliases to execute arbitrary commands. Details Since #26848, registryAliases has become mergeable. This means that the helmv3 manager started honoring its value and uses a helm repo add <key <parameters command for each defined alias. See source code: https://github.com/renovatebot/renovate/blob/23f3df6216375cb5bcfe027b0faee304f877f891/lib/modules/manager/helmv3/artifacts.ts#L80 The key was not quoted, leading to the ability to use variable references ($FOO) in it and have them printed by Renovate on the pull request, or even running any shell commands. PoC Inside a repository where Renovate runs, add a Helm chart with an outdated dependency, for example: test-chart/Chart.yaml: test-chart/Chart.lock: Then add the following renovate.json: Once Renovate runs on the repository, it will create a pull request, and add a comment titled "Artifact update problem" containing the…
Recommended action: Upgrade to 37.199.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Applies to Azure DevOps users only. The bot's token may be exposed in server or pipeline logs due to the http.extraheader=AUTHORIZATION parameter being logged without redaction. It is recommended that Azure DevOps users revoke their existing bot credentials and generate new ones after upgrading if there's a potential that logs have been saved to a location that others can view. Patches Fixed in Workarounds Do not share Renovate logs with anyone who cannot be trusted with access to the token.
Recommended action: Upgrade to 23.25.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Temporary repository tokens were leaked into Pull Requests comments in during certain Go Modules update failure scenarios. Patches The problem has been patched. Self-hosted users should upgrade to v19.38.7 or later. Workarounds Disable Go Modules support. References Blog post: https://renovatebot.com/blog/go-modules-vulnerability-disclosure For more information If you have any questions or comments about this advisory: Open an issue in Renovate
Recommended action: Upgrade to 19.38.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.