Renovate versions from 43.65.0 before 43.102.11 contain a remote code execution vulnerability in bazel-module and bazelisk managers when using lockFileMaintenance. Attackers can execute arbitrary code by providing malicious dependencies that are referenced in bazel mod deps calls, such as within ctx.execute statements.
CVE-2026-76226
Score 6.3 from GitHub Security Advisory published 2026-08-19. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Renovate 43.65.0 through 43.102.11 Remote Code Execution via lockFileMaintenance | Advisories | VulnCheck
https://www.vulncheck.com/advisories/renovate-through-remote-code-execution-via-lockfilemaintenanceRemote code execution was possible using the bazel-module or bazelisk managers, when using `lockFileMaintenance` · Advisory · renovatebot/renovate · GitHub
https://github.com/renovatebot/renovate/security/advisories/GHSA-5vjq-5jmg-39xqVendor Advisories for CVE-2026-76226(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| renovate | — | 43.102.11 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:17 UTCEG score recompute
- 2026-08-20 18:17 UTCGHSA enrichment
- 2026-08-20 17:32 UTCEG score recompute
- 2026-08-20 17:32 UTCGHSA enrichment
- 2026-08-20 14:00 UTCEG score recompute
- 2026-08-20 14:00 UTCGHSA enrichment
- 2026-08-19 14:25 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-76226?
When was CVE-2026-76226 disclosed?
Is CVE-2026-76226 actively exploited?
What is the CVSS score of CVE-2026-76226?
How do I remediate CVE-2026-76226?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76226
Is Your Infrastructure Affected by CVE-2026-76226?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.