CVE-2024-58376: Renovate Command Injection Vulnerability

CVE-2024-58376 Overview

CVE-2024-58376 is a command injection vulnerability [CWE-78] in Renovate, an automated dependency update tool. Affected versions include Renovate 37.158.0 through versions before 37.199.0. The flaw resides in the helmv3 manager's handling of registryAliases configuration values. Attackers with commit access to a repository processed by Renovate can supply registryAliases keys containing unquoted shell metacharacters. These characters are passed into helm repo add operations, resulting in arbitrary command execution within Renovate's execution environment.

Critical Impact
Successful exploitation grants full command execution in Renovate's runtime context, exposing repository credentials, tokens, and downstream CI/CD infrastructure.

Affected Products

Renovate 37.158.0 through versions before 37.199.0
Self-hosted Renovate deployments processing untrusted repositories
CI/CD pipelines invoking the helmv3 manager

Discovery Timeline

2026-08-19 - CVE-2024-58376 published to NVD
2026-08-20 - Last updated in NVD database

Technical Details for CVE-2024-58376

Vulnerability Analysis

Renovate's helmv3 manager supports a registryAliases configuration option that maps alias names to Helm chart registry URLs. When Renovate processes a Helm chart, it iterates over these aliases and invokes helm repo add for each entry. The vulnerability originates in how alias keys are interpolated into the shell command line without sanitization or quoting. A repository contributor can define an alias key that embeds shell metacharacters such as backticks, semicolons, or $() substitution. When Renovate executes the resulting command, the shell interprets these metacharacters and runs attacker-controlled commands. The vulnerability is classified under CWE-78: OS Command Injection.

Root Cause

The root cause is unsafe construction of a shell command string using untrusted input from repository configuration. The helmv3 manager treats registryAliases keys as trusted identifiers, but Renovate accepts these values from configuration files committed to the target repository. No allowlist validation or shell-escaping is applied before the value reaches the child process invocation.

Attack Vector

An attacker requires commit access to a repository monitored by Renovate. The attacker adds or modifies a Renovate configuration file to include a malicious registryAliases entry. On the next Renovate run, the injected payload executes with the privileges of the Renovate process. This exposes environment variables, source control tokens, and any credentials mounted into the execution environment. See the GitHub Security Advisory and the VulnCheck Advisory on Command Injection for additional detail.

Detection Methods for CVE-2024-58376

Indicators of Compromise

Unexpected child processes spawned by the Renovate worker process, particularly shells such as /bin/sh or /bin/bash executing commands unrelated to helm.
registryAliases keys in renovate.json, .renovaterc, or package.json containing shell metacharacters such as `, ;, |, &, $(, or >.
Outbound network connections from the Renovate execution environment to unrecognized hosts during dependency update runs.

Detection Strategies

Review historical repository commits for modifications to Renovate configuration that introduce registryAliases entries with non-alphanumeric characters.
Inspect Renovate execution logs for helm repo add invocations containing anomalous alias names.
Alert on process trees where helm or the Renovate binary spawn interpreters, package managers, or network utilities.

Monitoring Recommendations

Instrument CI/CD runners with process-level telemetry and forward events to a centralized detection pipeline.
Baseline the expected process tree of Renovate jobs and flag deviations for investigation.
Monitor secret access patterns from Renovate service accounts and revoke tokens on anomalous usage.

How to Mitigate CVE-2024-58376

Immediate Actions Required

Upgrade Renovate to version 37.199.0 or later on all self-hosted deployments.
Rotate any credentials, tokens, and secrets exposed to vulnerable Renovate runners.
Audit repositories processed by Renovate for malicious registryAliases entries introduced during the exposure window.

Patch Information

The issue is fixed in Renovate 37.199.0. Users of the hosted Mend Renovate service receive the fix automatically. Self-hosted operators must update container images, npm packages, or GitHub Action versions to a patched release. Refer to the GitHub Security Advisory GHSA-rqgv-292v-5qgr for release details.

Workarounds

Disable the helmv3 manager in Renovate configuration for repositories where it is not required.
Restrict commit access to protected branches and require code review for changes to Renovate configuration files.
Run Renovate in isolated, ephemeral containers with minimal secrets and network egress restrictions.

bash

# Configuration example: disable helmv3 manager as a temporary workaround
# renovate.json
{
  "enabledManagers": ["npm", "dockerfile", "github-actions"]
}