Medium

Renovate affected by remote code execution was possible using the bazel-module or bazelisk managers, when using lockFileMaintenance

  • Disclosed: 16.04.2026
  • Updated: 11.10.2026 10:22

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.

This does not affect any versions of Mend Renovate Self-Hosted.

Workarounds

  • Upgrade your Renovate version
  • Disable lockFileMaintenance for these managers

Why did this happen?

This was missed in code review (as part of https://github.com/renovatebot/renovate/pull/41507).

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package renovate >= 43.65.0, < 43.102.11 43.102.11

References

CVSS score 6.3/10
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H
Weakness (CWE)
CWE-94
Platform
npm
Package
renovate
Disclosed
16.04.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-5vjq-5jmg-39xq - CC BY 4.0

Vulnerability history: renovate

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (11) in the archive
Total entries
11
First → latest
10.2019 04.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Medium 11

Disclosures per year

  1. 2019: 1
  2. 2020: 1
  3. 2021: 0
  4. 2022: 0
  5. 2023: 0
  6. 2024: 1
  7. 2025: 0
  8. 2026: 8
Severity:
  1. Renovate affected by remote code execution was possible using the bazel-module or bazelisk managers, when using lockFileMaintenance this entry
    Medium · 6.3 CVE-2026-76226 >= 43.65.0, < 43.102.11 43.102.11
  2. Medium · 5.5 CVE-2026-76227 >= 42.68.1, < 42.96.3, >= 43.0.0, < 43.4.4 42.96.3, 43.4.4
  3. Medium · 5.4 CVE-2024-58376 >= 37.158.0, < 37.199.0 37.199.0
  4. Medium CVE-2020-37267 >= 19.180.0, < 23.25.1 23.25.1
  5. Medium · 5.3 CVE-2019-25766 >= 13.87.0, < 19.38.7 19.38.7

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.