Is this vulnerability remotely exploitable?

Yes. An attacker who can open or modify a pull request that changes `pyproject.toml` can potentially trigger exploitation when the affected GitHub Actions workflow runs, without needing direct access to the CI environment.

What level of access does an attacker need to exploit this?

The attacker needs the ability to influence repository contents that are used by the workflow, typically via a pull request. In many open-source projects, anyone can create a PR from a fork, which is sufficient if the workflow runs in a context that uses the untrusted configuration.

What is the safest general fix pattern?

The safest pattern is to avoid deriving executable tool versions or sources from files that untrusted contributors can modify. Pin CI tooling versions directly in the workflow definition, and restrict installation sources to trusted registries or artifact repositories.

Severity:

CRITICAL RISK

(9.8)

Improper Input Validation (CWE-20) in Black GitHub Action use_pyproject Option

CVE-2026-31900

Published:

Mar 11, 2026

Status:

Analyzed

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-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Improper Input Validation

CWE:

CWE-20

Impact:

Remote Code Execution in CI/CD Pipeline

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Input Validation

CWE:

CWE-20

Impact:

Remote Code Execution in CI/CD Pipeline

Severity:

CRITICAL RISK

(9.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 Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Improper Input Validation (CWE-20) in Black GitHub Action use_pyproject Option

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

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal