Skip to main content
VulnerabilityPublished

CVE-2026-42603: BLT · Code Injection

Affects BLTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.1.2 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade BLT and owasp-blt/BLT to 2.1.2.

Affected software

ProductAffectedFixed in
OWASP-BLTBLTAffected
  • <2.1.2
Fixed in
  • 2.1.2
GitHubowasp-blt/BLTpkg:github/owasp-blt/BLTOther threatsAffected
  • <2.1.2
Fixed in
  • 2.1.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

Description

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.

References

Community reviews

Loading reviews…