# CVE-2026-76226: Renovate 43.65.0 before 43.102.11 Remote Code Execution via lockFileMaintenance

> Attackers can execute arbitrary code in Renovate via malicious Bazel dependencies when lockFileMaintenance is enabled.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-5vjq-5jmg-39xq, GHSA-7g3f-prg4-fg23

## What is CVE-2026-76226?

CVE-2026-76226 is a medium-severity command injection vulnerability in renovatebot renovate, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-76226?

2 open source packages ship an affected version, including renovate.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `renovate` | npm | From 43.65.0 | 43.102.11 |
| `renovate` | npm | From 43.65.0 | 43.102.11 |

## How do I fix CVE-2026-76226?

Upgrade renovate to 43.102.11 or later.

## Is CVE-2026-76226 being exploited?

There is no known exploitation of CVE-2026-76226 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76226 and fix it if it is affected.

What it is: CVE-2026-76226 is a medium-severity command injection vulnerability in renovatebot renovate, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76226 in the wild and no public exploit code.

Affected packages and fixed versions:
- renovate (npm): affected from 43.65.0; fixed in 43.102.11
- renovate (npm): affected from 43.65.0; fixed in 43.102.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76226/ (Markdown: https://insights.sbomify.com/CVE-2026-76226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76226
- OSV: https://osv.dev/vulnerability/CVE-2026-76226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76226/
Summaries are generated and may contain mistakes; the official description above is the record.