GHSA-5VJQ-5JMG-39XQ

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.

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).

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.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

GHSA-5VJQ-5JMG-39XQ has a CVSS score of 6.3 (Medium). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (43.102.11); upgrading removes the vulnerable code path.

Kodem intelligence

This is patched in 43.102.11.

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

1. What is GHSA-5VJQ-5JMG-39XQ? GHSA-5VJQ-5JMG-39XQ is a medium-severity code injection vulnerability in renovate (npm), affecting versions >= 43.65.0, < 43.102.11. It is fixed in 43.102.11. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is GHSA-5VJQ-5JMG-39XQ? GHSA-5VJQ-5JMG-39XQ has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of renovate are affected by GHSA-5VJQ-5JMG-39XQ? renovate (npm) versions >= 43.65.0, < 43.102.11 is affected.
4. Is there a fix for GHSA-5VJQ-5JMG-39XQ? Yes. GHSA-5VJQ-5JMG-39XQ is fixed in 43.102.11. Upgrade to this version or later.
5. Is GHSA-5VJQ-5JMG-39XQ exploitable, and should I be worried? Whether GHSA-5VJQ-5JMG-39XQ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-5VJQ-5JMG-39XQ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-5VJQ-5JMG-39XQ? Upgrade renovate to 43.102.11 or later.