CVE-2026-76229: renovatebot renovate · Command Injection
Affects renovatebot renovateSource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 40.33.0 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 40.33.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade renovate and renovatebot/renovate to 40.33.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| renovatebotrenovate | Affected
| Fixed in
|
GitHubrenovatebot/renovatepkg:github/renovatebot/renovateOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Renovate versions starting from 40.33.0. Users should upgrade to version 40.33.0 or later to remediate this vulnerability. No additional mitigation steps are indicated in the provided data.
Description
Renovate versions from 39.218.0 up to but not including 40.33.0 contain a command injection vulnerability in the kustomize manager. This vulnerability allows attackers with repository write access to execute arbitrary commands on the Renovate host by leveraging malicious kustomization.yaml files with specially crafted chart names. The flaw arises because these chart names are appended unsafely to helm pull commands. The issue has a high severity score of 8.4.