Is this vulnerability remotely exploitable?

It can be, depending on how the application uses simple-git. If remote users can influence values that are passed into simple-git (e.g., branch names derived from requests, repository URLs supplied via APIs, or data from webhooks), then the issue can often be exploited over the network.

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

The attacker needs the ability to control input that flows into simple-git calls. This may be unauthenticated (public endpoints) or authenticated (developer portals, CI triggers, admin tools), but the key requirement is control over data that becomes part of the constructed git command or its arguments.

What is the safest general fix pattern?

The safest pattern is to ensure that git commands are built from strictly validated, constrained inputs and executed without relying on shell interpretation. This means using argument-based execution models, enforcing allowlists for all user-influenced values, and centralizing simple-git usage behind hardened helper functions.

Severity:

CRITICAL RISK

(9.8)

Command Injection (CWE-78) in simple-git Node.js Library

CVE-2026-28292

Published:

Mar 10, 2026

Status:

Modified

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:

Command Injection

CWE:

CWE-78;CWE-178

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Command Injection

CWE:

CWE-78;CWE-178

Impact:

Remote Code Execution

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

Command Injection (CWE-78) in simple-git Node.js Library

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