Code execution via unsafe bazel mod deps
Published Aug 19, 2026 · Updated Aug 20, 2026
Code execution in bazel-module and bazelisk in Mend.io Renovate 43.65.0 through 43.102.10 allows attackers to run commands via malicious Bazel dependencies. During lockFileMaintenance, Renovate regenerates MODULE.bazel.lock by running the external bazel mod deps command, so attacker-controlled module code referenced during dependency resolution can execute, including ctx.execute calls named in the CVE record. Exposure requires the bazel-module or bazelisk manager with lock file maintenance enabled and, for self-hosted use, explicit opt-in to allowedUnsafeExecutions for bazelModDeps; published scoring treats exploitation as local and high-privilege rather than unauthenticated internet-reachable.
Summary
What happened
Code execution in bazel-module and bazelisk in Mend.io Renovate 43.65.0 through 43.102.10 allows attackers to run commands via malicious Bazel dependencies. During lockFileMaintenance, Renovate regenerates MODULE.bazel.lock by running the external bazel mod deps command, so attacker-controlled module code referenced during dependency resolution can execute, including ctx.execute calls named in the CVE record. Exposure requires the bazel-module or bazelisk manager with lock file maintenance enabled and, for self-hosted use, explicit opt-in to allowedUnsafeExecutions for bazelModDeps; published scoring treats exploitation as local and high-privilege rather than unauthenticated internet-reachable.
The record
- CVE
- CVE-2026-76226
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Mend.io
- Product
- Renovate
- Classifications
- CWE-94, CWE-78
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=43.65.0 <43.102.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo