Runner code execution via untrusted pull-request checkout
Published Mar 6, 2026 · Updated Mar 6, 2026
Code injection in Mesa 3.5.0 and earlier allows remote attackers to execute arbitrary code in a privileged GitHub Actions runner. The benchmarks.yml workflow checks out a pull-request branch, then pip installs it and runs global_benchmark.py from that untrusted branch. Opening or marking a crafted pull request ready triggers the job, granting injected code the runner token's write access to issues and pull requests.
Summary
What happened
Code injection in Mesa 3.5.0 and earlier allows remote attackers to execute arbitrary code in a privileged GitHub Actions runner. The benchmarks.yml workflow checks out a pull-request branch, then pip installs it and runs global_benchmark.py from that untrusted branch. Opening or marking a crafted pull request ready triggers the job, granting injected code the runner token's write access to issues and pull requests.
The record
- CVE
- CVE-2026-29075
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- Mesa
- Product
- Mesa
- Classifications
- T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 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=<= 3.5.0
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