Renovate versions before 44.79.0 contain a server-side request forgery (SSRF) vulnerability. This flaw allows users to make the shared HTTP client request arbitrary internal URLs via extends presets or customDatasources. Exploitation can lead to attackers accessing instance metadata service endpoints to obtain AWS credentials or leak sensitive information through Renovate logs. The vulnerability has a high severity with a CVSS score of 8.4. A patch is available to address this issue.
CVE-2026-110867 is a critical authorization bypass vulnerability in renovatebot's renovate tool before version 44.60.1. It allows attackers controlling an externally sourced preset to bypass environment variable restrictions by placing env inside a shared preset. This enables overriding sensitive environment variables such as PATH, LD_PRELOAD, NODE_OPTIONS, or GIT_SSL_CAINFO in child processes on self-hosted instances.
Renovate versions before 44.61.3 contain a vulnerability that allows bypassing the minimumReleaseAge protection mechanism when a user requests a PR rebase via the rebase/retry checkbox. This flaw can enable malicious dependency versions to be introduced into pull requests and executed in continuous integration environments before the intended release age has elapsed.
CVE-2026-110865 is a high-severity vulnerability in renovatebot's renovate tool before version 44.60.1. It allows repository users to bypass the allowedHeaders restriction by embedding hostRules headers inside shared presets. This enables attackers to inject custom HTTP headers into requests sent by Renovate to other hosts.
Renovate before 44.14.7 contains a command injection vulnerability in the Maven Wrapper manager that allows attackers to execute arbitrary commands by specifying a malicious distributionType parameter in maven-wrapper.properties. Attackers can inject shell commands through unescaped distributionType values to achieve remote code execution when Renovate processes Maven Wrapper updates in binarySource=docker mode.
Renovate before 44.14.7 contains a command injection vulnerability in the Mix manager when processing private dependencies with unescaped organization parameters. Attackers can inject shell metacharacters through malicious package names to execute arbitrary commands as the Renovate user in binarySource=docker mode.
Renovate is a dependency update automation tool. When listing tags/digests for a container image, Renovate follows pagination links supplied by the remote registry in the HTTP Link header and attaches the registry credentials to the follow-up request without verifying that the pagination URL has the same origin as the original registry. A malicious or compromised container registry can therefore specify a Link header pointing to an attacker-controlled host and receive the credentials Renovate uses for that registry. Exploitation requires that the target has container (Docker) dependencies and is already interacting with the malicious or compromised registry. This is fixed in Renovate 44.11.2 (npm and renovate/renovate images), Mend Renovate CE/EE 15.4.0 and the mend-renovate-enterprise-edition Helm chart 10.4.0; the same-origin check can be disabled with RENOVATE_X_DOCKER_PAGINATION_ALLOW_CROSS_ORIGIN.
Renovate is a dependency update automation tool. In versions before 44.14.7 (and in Mend Renovate CE/EE distributions before 15.4.0, and the mend-renovate-enterprise-edition Helm chart before 10.4.0), the manager/gradle-wrapper module does not escape the distributionUrl value read from a repository's gradle/wrapper/gradle-wrapper.properties file before invoking the Gradle Wrapper CLI. In self-hosted deployments configured with binarySource=docker and allowedUnsafeExecutions=['gradleWrapper', ...], a repository that supplies a crafted distributionUrl (for example, appending a shell metacharacter and command) can cause arbitrary commands to be executed as the Renovate user when Renovate processes a Gradle Wrapper update. The issue is fixed in Renovate 44.14.7; as a workaround, remove 'gradleWrapper' from allowedUnsafeExecutions.
Renovate before 44.14.7 contains a command injection vulnerability in the gomod manager when processing unescaped depName parameters in import-path update commands with binarySource=docker mode. Attackers can inject shell metacharacters through malicious dependency names to execute arbitrary commands as the Renovate user during Go module major version updates with postUpdateOptions gomodUpdateImportPaths enabled.
Renovate is a dependency update automation tool. In versions before 44.3.1 (and Mend Renovate CE/EE images before 15.4.0, mend-renovate-ce Helm chart before 15.4.0, mend-renovate-enterprise-edition Helm chart before 10.4.0), digest updates are not subject to the internal `minimumReleaseAge` (stability age) checks. When a repository configures `minimumReleaseAge` and has dependencies with `updateType=digest` — for example GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules or NuGet packages — Renovate will still open a pull request for a newly published digest, marked only with a pending `renovate/stability-days` status check. A newly published, potentially malicious dependency version can therefore cause a PR to be raised and CI workflows to potentially run before the configured minimum release age has elapsed, which is precisely what the Minimum Release Age control is intended to prevent. The issue is fixed in Renovate 44.3.1; as a workaround, digest updates can be disabled or gated behind `dependencyDashboardApproval`.
Renovate is an automated dependency update tool. In versions before 44.14.4 (and Mend Renovate CE/EE images before 15.4.0 and the mend-renovate-enterprise-edition Helm chart before 10.4.0), log sanitisation for TLS private keys used for Mutual TLS was incomplete. While the value of hostRules[].httpsPrivateKey was redacted in the field itself, the same private key value was not redacted if it also appeared elsewhere — for example in another configuration option or in a log message under a key other than httpsPrivateKey — causing the full private key to be written to Renovate's logs in cleartext. This affects deployments that configure Mutual TLS through hostRules[].httpsPrivateKey without passing the value through the documented `secrets` configuration. Anyone able to read the resulting logs can recover the private key. The issue is fixed in Renovate 44.14.4, which redacts any value supplied as hostRules[].httpsPrivateKey wherever it appears in the logs; as a workaround, supply the key via the `secrets` configuration.
Renovate is a dependency update automation tool. In versions before 44.11.2 (and Mend Renovate CE/EE images and charts before 15.4.0, and mend-renovate-enterprise-edition helm chart before 10.4.0), when listing new package versions from a NuGet registry Renovate follows pagination URLs supplied by the registry in the HTTP `Link` header without verifying that the target has the same origin as the configured registry. Registry credentials are attached to the request for the 'next' page, so a malicious or compromised NuGet registry can return a `Link` header pointing at an attacker-controlled server and cause Renovate to send the registry credentials to that server. Exploitation requires the remote registry to be malicious or compromised; such a registry would normally already have received the credentials on the initial request, so the issue primarily allows the credentials to be delivered to an additional, attacker-chosen host. The fix restricts pagination to the same origin; the previous behaviour can be re-enabled with the RENOVATE_X_NUGET_PAGINATION_ALLOW_CROSS_ORIGIN option.
Renovate, a dependency update tool, follows pagination links supplied by the GitHub server in the HTTP `Link` header when interacting with GitHub.com, GitHub Enterprise Cloud, or GitHub Enterprise Server, and sends the credentials configured for that host to the URL given as the 'next' page. Because the pagination URL is not validated against the host originally contacted, a malicious or compromised GitHub server can return a `Link` header pointing to an attacker-controlled host and cause Renovate to disclose those credentials to it. Exploitation requires that the GitHub server Renovate talks to (as the repository host or as a datasource such as github-releases, github-tags, or git-refs) is already malicious or compromised. The issue is fixed in renovate 44.11.3 (npm and renovate/renovate container images), Mend Renovate CE/EE images and the mend-renovate-ce helm chart 15.4.0, and the mend-renovate-enterprise-edition helm chart 10.4.0. There is no workaround; the pre-existing RENOVATE_X_REBASE_PAGINATION_LINKS option disables the new host check and should only be used with servers that intentionally use different pagination hosts.
Renovate before 44.11.3 fails to validate Link header destinations when following GitLab server pagination, allowing malicious servers to redirect credential-bearing requests. Attackers controlling a compromised GitLab server can specify a Link header pointing to attacker-controlled infrastructure to exfiltrate authentication credentials.
Renovate versions 39.53.0 up to but not including 40.33.0 have a command injection vulnerability in the gleam manager. The depName parameter is not properly sanitized, allowing an attacker with repository write access to execute arbitrary commands on the host running Renovate by crafting malicious gleam.toml files. This vulnerability has a high severity with a CVSS score of 8.4.
Renovate versions from 31.51.0 up to but not including 40.33.0 have a command injection vulnerability in the helmv3 manager. This vulnerability arises because the repository parameter is appended to helm registry login commands without proper sanitization. An attacker with repository write access can exploit this by crafting malicious Chart.yaml files to execute arbitrary commands on the machine running Renovate. The vulnerability has a high severity score of 8.4.
Renovate versions from 32.135.0 up to but not including 40.33.0 contain a command injection vulnerability in the hermit manager component. This flaw allows attackers with repository write access to execute arbitrary commands by exploiting improper sanitization of malicious dependency names. The vulnerability has a CVSS 4.0 score of 8.4, indicating high severity.
Renovate versions from 35.63.0 up to but not including 40.33.0 contain a command injection vulnerability in the npm manager. This vulnerability allows attackers with repository write access to craft malicious Renovate configuration files that execute arbitrary commands on the host system due to improper sanitization of packageName values in npm install commands. The flaw has a high severity with a CVSS 4.0 score of 8.4.
Renovate versions from 39.218.0 up to but not including 40.33.0 contain a command injection vulnerability in the kustomize manager. This vulnerability allows attackers with repository write access to execute arbitrary commands on the Renovate host by leveraging malicious kustomization.yaml files with specially crafted chart names. The flaw arises because these chart names are appended unsafely to helm pull commands. The issue has a high severity score of 8.4.
CVE-2026-76228 is a command injection vulnerability in renovatebot's Renovate tool affecting versions >=32.124.0 and <42.68.5, and Mend renovate-ce/renovate-ee versions <13.3.0. The flaw occurs in the handling of Gradle Wrapper artifacts, where a malicious gradle-wrapper.properties file with a crafted distributionUrl can cause arbitrary command execution during Renovate's Gradle Wrapper update process. Exploitation requires an attacker to introduce this malicious file into a repository scanned by Renovate. This vulnerability is rated high severity with a CVSS score of 8.4. No patch links or vendor advisory details are provided, so patch status is not confirmed.