GPU VulnDB

Database/Control plane, storage & DevOps

Renovate: unescaped Gradle distributionUrl gives a repository command execution as the Renovate user

CVSS 8.5CVE-2026-88886Control plane, storage & DevOpscurated

Impact

A self-hosted Renovate bot runs against every repository it is configured to update, and on a GPU fleet those repositories are usually the ones holding cluster manifests, image build definitions and deployment config. Any repository that Renovate processes can put a shell metacharacter in gradle/wrapper/gradle-wrapper.properties and get arbitrary commands executed as the Renovate user, inside the Renovate container. That process normally holds Git push credentials and platform tokens for all managed repositories, so a single writable repository turns into write access to the rest of the CI surface. Only deployments running with binarySource=docker and gradleWrapper listed in allowedUnsafeExecutions are affected.

Who can reach it

Anyone who can commit to a repository that the self-hosted Renovate instance scans - in practice any developer with push rights to any onboarded repo, or an attacker who has taken over one. No access to the Renovate host itself is needed.

What to do

Upgrade Renovate to 44.14.7, Mend Renovate CE/EE to 15.4.0, or the mend-renovate-enterprise-edition Helm chart to 10.4.0, then restart the Renovate service or roll the deployment. If an upgrade cannot be scheduled, remove 'gradleWrapper' from allowedUnsafeExecutions, which the advisory gives as a workaround. No node reboot or drain is involved; rotate any Git or registry credentials the Renovate user held if you cannot rule out exploitation.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.