Skip to content

← Actionable
Medium, CVSS 6.3amended

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

CVE-2026-76226GHSA-5vjq-5jmg-39xq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (renovate 43.102.11), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm renovate

    Affected
    >= 43.65.0, < 43.102.11
    Fixed in
    43.102.11

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.3 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H
EPSS
  • CVE-2026-76226: 0.29% estimated exploitation activity in the next 30 days; percentile 22.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5vjq-5jmg-39xq

  2. Revision 1 · created ·

    Published from osv record GHSA-5vjq-5jmg-39xq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-76226

Advisory: Renovate affected by remote code execution was possible using the bazel-module or bazelisk managers, when using lockFileMaintenance
IDs: CVE-2026-76226, GHSA-5vjq-5jmg-39xq
Record: https://patchnext.com/advisories/cve-2026-76226 (revision 2, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: renovate 43.102.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm renovate: affected >= 43.65.0, < 43.102.11; fixed in 43.102.11

## Suggested inspection (read-only)
- `npm ls renovate --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on renovate.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5vjq-5jmg-39xq (OSV record GHSA-5vjq-5jmg-39xq lists affected ranges: npm renovate >=43.65.0 <43.102.11 (fixed))
- Verified: https://github.com/advisories/GHSA-5vjq-5jmg-39xq (GitHub-reviewed advisory GHSA-5vjq-5jmg-39xq lists affected ranges: npm renovate >=43.65.0 <43.102.11)

Commands are suggestions: review each one before running it.

Loading voting…