Mesa: Auschecken von nicht vertrauenswürdigem Code in `benchmarks.yml` Workflow kann zu Codeausführung im privilegierten Runner führen

An attacker could exploit this vulnerability by crafting malicious code within the benchmarks.yml workflow. When a user checks out this workflow, the attacker's code would be executed on the privileged runner, potentially granting the attacker full control over the system. This could lead to data theft, system compromise, or further lateral movement within the network. The blast radius extends to any system running vulnerable Mesa instances, particularly those used in automated testing or continuous integration pipelines where the benchmarks.yml workflow is executed.

Organizations and individuals utilizing Mesa for agent-based modeling, particularly those running simulations in environments with limited access controls or where the runner environment has elevated privileges. Researchers and developers who have customized the benchmarks.yml workflow are also at increased risk.

• python / supply-chain:

import os
import subprocess

# Check Mesa version
result = subprocess.run(['pip', 'show', 'mesa'], capture_output=True, text=True)
if result.returncode == 0:
    mesa_version = result.stdout.split('Version: ')[1].split('\n')[0]
    if float(mesa_version) <= 3.5:
        print("Mesa version is vulnerable.")
else:
    print("Mesa is not installed.")

• generic web: Check for unusual files or modifications within the Mesa installation directory, particularly related to the benchmarks.yml workflow.

1. 2026-03-06Disclosure

   disclosure

1. Reserviert2026-03-03
2. Veröffentlicht2026-03-06
3. Geändert2026-03-09
4. EPSS aktualisiert2026-03-23

The primary mitigation is to upgrade to a patched version of Mesa, specifically version 3.5.1 or later, which contains the fix committed as c35b8cd. If an immediate upgrade is not feasible, consider temporarily disabling the benchmarks.yml workflow or restricting access to it to trusted users only. Review and audit all code within the benchmarks.yml workflow to ensure its integrity. Implement strict code review processes for any external code included in this workflow. After upgrade, confirm by running the benchmarks workflow with a known-good repository to verify the fix.