Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-42603: CWE-94: Improper Control of Generation of Code ('Code Injection') in OWASP-BLT BLT

0
High
VulnerabilityCVE-2026-42603cvecve-2026-42603cwe-94cwe-95
Published: Mon May 11 2026 (05/11/2026, 16:11:55 UTC)
Source: CVE Database V5
Vendor/Project: OWASP-BLT
Product: BLT

Description

CVE-2026-42603 is a high-severity vulnerability in OWASP BLT prior to version 2. 1. 2. It involves improper control of code generation leading to code injection via the . github/workflows/pre-commit-fix. yaml file. The workflow uses the privileged pull_request_target trigger but executes code directly from an attacker's fork, enabling remote code execution with write permissions. This vulnerability has been fixed in version 2. 1. 2.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/11/2026, 18:21:24 UTC

Technical Analysis

OWASP BLT versions before 2.1.2 contain a code injection vulnerability (CWE-94) due to the use of the pull_request_target GitHub Actions trigger in the .github/workflows/pre-commit-fix.yaml workflow. This trigger runs with elevated privileges but checks out and executes code from the attacker's fork repository without proper validation, allowing an attacker to execute arbitrary code remotely with write access. The issue is resolved in version 2.1.2 of OWASP BLT.

Potential Impact

Successful exploitation allows an attacker to achieve remote code execution with write permissions on the affected system. This can lead to full compromise of the environment where the workflow runs, including unauthorized code execution and potential further attacks. The CVSS v3.1 score is 8.8 (high), reflecting the network attack vector, low attack complexity, no privileges required, user interaction required, and high impact on confidentiality, integrity, and availability.

Mitigation Recommendations

Upgrade OWASP BLT to version 2.1.2 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 2.1.2, applying this update fully mitigates the risk. No additional mitigations are specified or required beyond upgrading.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-29T00:31:15.725Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a021aadcbff5d8610430a44

Added to database: 5/11/2026, 6:06:37 PM

Last enriched: 5/11/2026, 6:21:24 PM

Last updated: 5/11/2026, 7:09:11 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses