CVE-2026-29075
Privilege escalation via untrusted benchmarks.yml checkout enabling code execution in privileged runner.
Is CVE-2026-29075 being exploited?
Not confirmed. CVE-2026-29075 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-29075?
CVE-2026-29075 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-29075?
Yes. A fix has been recorded for CVE-2026-29075. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-29075 affect?
CVE-2026-29075 affects Mesa Python library <= 3.5.0, Mesa benchmarks.yml workflow. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-29075?
Update Mesa to a patched version (>=3.5.1)
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Code execution in a privileged runner via untrusted benchmarks.yml checkout in Mesa <= 3.5.0.
Patch when possible
- affected<= 3.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.