Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Renovate vulnerable to arbitrary command injection via helmv3 manager and registryAliases

CVE-2024-58376GHSA-rqgv-292v-5qgr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (renovate 37.199.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
    >= 37.158.0, < 37.199.0
    Fixed in
    37.199.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2024-58376: 0.69% estimated exploitation activity in the next 30 days; percentile 52.67 (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 Attackers with commit access to the default branch of a repo using Renovate could manipulate helmv3 registryAliases to execute arbitrary commands. Details Since #26848, registryAliases has become mergeable. This means that the helmv3 manager started honoring its value and uses a helm repo add <key <parameters command for each defined alias. See source code: https://github.com/renovatebot/renovate/blob/23f3df6216375cb5bcfe027b0faee304f877f891/lib/modules/manager/helmv3/artifacts.ts#L80 The key was not quoted, leading to the ability to use variable references ($FOO) in it and have them printed by Renovate on the pull request, or even running any shell commands. PoC Inside a repository where Renovate runs, add a Helm chart with an outdated dependency, for example: test-chart/Chart.yaml: test-chart/Chart.lock: Then add the following renovate.json: Once Renovate runs on the repository, it will create a pull request, and add a comment titled "Artifact update problem" containing the…

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

    Amended from ghsa record GHSA-rqgv-292v-5qgr

  2. Revision 1 · created ·

    Published from osv record GHSA-rqgv-292v-5qgr

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-2024-58376

Advisory: Renovate vulnerable to arbitrary command injection via helmv3 manager and registryAliases
IDs: CVE-2024-58376, GHSA-rqgv-292v-5qgr
Record: https://patchnext.com/advisories/cve-2024-58376 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: renovate 37.199.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm renovate: affected >= 37.158.0, < 37.199.0; fixed in 37.199.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-rqgv-292v-5qgr (OSV record GHSA-rqgv-292v-5qgr lists affected ranges: npm renovate >=37.158.0 <37.199.0 (fixed))
- Verified: https://github.com/advisories/GHSA-rqgv-292v-5qgr (GitHub-reviewed advisory GHSA-rqgv-292v-5qgr lists affected ranges: npm renovate >=37.158.0 <37.199.0)

Commands are suggestions: review each one before running it.

Loading voting…