Renovate: shell metacharacters in helmv3 registryAliases give commit-access users command execution

Impact

Renovate's helmv3 manager interpolates registryAliases keys into the helm repo add command line without quoting, so a key containing shell metacharacters executes commands during a dependency scan. Anyone who can land a commit in a repository the bot scans gets full access to Renovate's execution environment. On a self-hosted bot that environment normally holds the tokens Renovate needs across the whole estate — a git platform token with write access to every repository, and registry credentials — so a single writable repo converts into broad control over the pipelines that feed GPU runners. Affected: 37.158.0 up to 37.199.0.

Who can reach it

An attacker with commit access to any repository in the self-hosted bot's scan scope. Authenticated, and only as much privilege as a normal contributor.

What to do

Upgrade self-hosted Renovate to 37.199.0 or later; for containerised deployments that means pulling the new image and restarting the scheduled job or worker. No node maintenance. Rotate the platform and registry tokens the bot holds if you cannot rule out a scan of an untrusted repository on a vulnerable version.

References