GitHub Actions pull_request_target RCE in OWASP BLT pre-commit-fix workflow
CVE-2026-42603 affects OWASP BLT versions prior to 2.1.2. The vulnerable component is the GitHub Actions workflow file .github/workflows/pre-commit-fix.yaml, which uses the privileged pull_request_target event and then checks out and executes code from an attacker's forked pull request. Because pull_request_target runs in the security context of the target repository, this workflow design allows untrusted attacker-controlled code to execute with elevated repository permissions. The issue can result in remote code execution within the GitHub Actions runner and access to the repository's write-capable workflow token or other secrets available to that job. The issue was fixed in version 2.1.2.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
.github/workflows/pre-commit-fix.yaml workflow, especially for fork-originated pull requests. Avoid using pull_request_target for workflows that execute PR code; prefer pull_request for untrusted code paths. Reduce GITHUB_TOKEN permissions to least privilege, disable write permissions where not required, prevent secrets from being exposed to jobs processing untrusted contributions, and require maintainer review before running workflows on external pull requests.Remediation
Patch, then assume compromise.
pull_request_target should not check out, build, or execute code from the untrusted head of a forked pull request. If privileged automation is required, separate untrusted validation from privileged post-processing, and ensure any privileged job operates only on trusted repository content.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.