Is this vulnerability remotely exploitable?

Yes. In repositories where the workflow can be triggered from issue comments, any user who can create or influence those comments may be able to trigger command execution, subject to repository and workflow configuration.

What access does an attacker need to exploit this?

The attacker needs the ability to post issue comments that the workflow consumes. In public projects, this often requires only a standard GitHub account, but private or restricted repositories may limit who can comment or trigger workflows.

What is the safest general fix pattern?

The safest pattern is to remove direct shell interpolation of user-controlled fields and instead pass user data as validated, constrained inputs to non-shell actions or scripts. Where shell usage is necessary, commands should be parameterized so the shell never interprets user content as part of the command itself.

Severity:

CRITICAL RISK

(9.8)

Command Injection in GitHub Actions Workflow (CWE-77) for wenxian Bibliography Tool

CVE-2026-34243

Published:

Mar 31, 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-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Command Injection

CWE:

CWE-77;CWE-78

Impact:

Remote Code Execution on CI Runner

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Command Injection

CWE:

CWE-77;CWE-78

Impact:

Remote Code Execution on CI Runner

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

Command Injection in GitHub Actions Workflow (CWE-77) for wenxian Bibliography Tool

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)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

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