Code Injection in OWASP BLT (CVE-2026-42603)
Summary
Code injection in OWASP BLT (CVE-2026-42603). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.1.2 or later.
Original description
The description as published by the source.
OWASP BLT is a QA testing and vulnerability disclosure platform that encompasses websites, apps, git repositories, and more. Prior to 2.1.2, .github/workflows/pre-commit-fix.yaml uses pull_request_target (privileged trigger) but checks out and executes code directly from the attacker's fork, enabling RCE with write permissions. This vulnerability is fixed in 2.1.2.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42603 has been found in OWASP BLT.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade OWASP BLT to 2.1.2 or later.
If unsure, ask your IT team or search "OWASP BLT CVE-2026-42603" on the vendor's site.
CVE-2026-42603 (OWASP BLT) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in OWASP BLT.
Check the vendor advisory for the affected versions of OWASP BLT.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OWASP BLT を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade OWASP BLT to 2.1.2ステージング環境で 2.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com