Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.7amended

Renovate vulnerable to arbitrary command injection via npm manager and malicious Renovate configuration

CVE-2026-76230GHSA-fr4j-65pv-gjjj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (renovate 40.33.0), 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.

Add to your agent

Affected packages

  • npm renovate

    Affected
    >= 35.63.0, < 40.33.0
    Fixed in
    40.33.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.7 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-76230: 1.01% estimated exploitation activity in the next 30 days; percentile 63.31 (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.

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

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

    Amended from ghsa record GHSA-fr4j-65pv-gjjj

  2. Revision 1 · created ·

    Published from osv record GHSA-fr4j-65pv-gjjj

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-76230

Advisory: Renovate vulnerable to arbitrary command injection via npm manager and malicious Renovate configuration
IDs: CVE-2026-76230, GHSA-fr4j-65pv-gjjj
Record: https://patchnext.com/advisories/cve-2026-76230 (revision 2, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: renovate 40.33.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm renovate: affected >= 35.63.0, < 40.33.0; fixed in 40.33.0

## 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-fr4j-65pv-gjjj (OSV record GHSA-fr4j-65pv-gjjj lists affected ranges: npm renovate >=35.63.0 <40.33.0 (fixed))
- Verified: https://github.com/advisories/GHSA-fr4j-65pv-gjjj (GitHub-reviewed advisory GHSA-fr4j-65pv-gjjj lists affected ranges: npm renovate >=35.63.0 <40.33.0)

Commands are suggestions: review each one before running it.

Loading voting…