How broadly exploitable is this vulnerability?

Any external contributor who can open a pull request against an affected OWASP BLT repository and whose PR receives the `regenerate-migrations` label can potentially exploit this issue. The limiting factor is maintainer action: a maintainer must apply the label to trigger the vulnerable workflow.

Does exploitation require repository write access or authentication beyond a standard GitHub account?

No repository write access is needed. A standard GitHub account with the ability to submit a pull request from a fork is sufficient. The attack leverages the repository's own CI permissions granted to the workflow, not the attacker's account privileges.

What is the safest general fix pattern for this type of issue?

The safest pattern is to prevent execution of untrusted PR code under high-privilege contexts. Concretely, avoid using `pull_request_target` (or equivalent) for workflows that build or execute PR content, minimize the permissions of any tokens used in workflows, and ensure that any privileged automation only processes trusted base-branch code.

Severity:

HIGH RISK

(8.8)

Code Injection via Untrusted Pull Request Workflow (CWE-94) in OWASP BLT GitHub Actions

CVE-2026-40316

Published:

Apr 15, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Code Injection / Insecure CI Workflow

CWE:

CWE-94;CWE-95

Impact:

Remote Code Execution in CI with Repository Token and Secrets Exposure

Severity:

HIGH RISK

(8.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Code Injection / Insecure CI Workflow

CWE:

CWE-94;CWE-95

Impact:

Remote Code Execution in CI with Repository Token and Secrets Exposure

Severity:

HIGH RISK

(8.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Code Injection via Untrusted Pull Request Workflow (CWE-94) in OWASP BLT GitHub Actions

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare