# CVE-2026-76229: Renovate 39.218.0 before 40.33.0 Arbitrary Command Injection via kustomize

> Attackers with repository write access can execute arbitrary commands on the Renovate host by crafting malicious kustomization.yaml files.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/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:** 20 Aug 2026
- **Also known as:** GHSA-5gfg-jpw3-fppq, GHSA-xv56-3wq5-9997

## What is CVE-2026-76229?

CVE-2026-76229 is a high-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 39.218.0 before 40.33.0 contain an arbitrary command injection vulnerability in the kustomize manager where user-provided chart names are appended to helm pull commands without proper sanitization. Attackers with repository write access can craft malicious kustomization.yaml files with specially crafted chart names to execute arbitrary commands on the Renovate host machine.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `renovate` | npm | From 39.218.0 | 40.33.0 |
| `renovate` | npm | From 39.218.0 | 40.33.0 |

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

Upgrade renovate to 40.33.0 or later.

## Is CVE-2026-76229 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76229 is a high-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-76229 in the wild and no public exploit code.

Affected packages and fixed versions:
- renovate (npm): affected from 39.218.0; fixed in 40.33.0
- renovate (npm): affected from 39.218.0; fixed in 40.33.0

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-76229/ (Markdown: https://insights.sbomify.com/CVE-2026-76229/index.md)
```

## Sources

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

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