Is this vulnerability remotely exploitable?

Not in the traditional network sense. Exploitation happens in the local development environment when the vulnerable pre-commit hook runs. However, if an attacker can influence the working tree (for example, through a compromised project template, malicious dependency writing files, or shared environment), they may cause other developers to unknowingly stage sensitive files.

What level of access does an attacker need?

The attacker needs the ability to create or rename files in the repository's working directory. In many collaborative or scripted environments, this may be achievable by any contributor, a malicious tool in the toolchain, or a process running as the developer.

What is the safest general fix pattern?

The safest fix is to ensure that all command invocations treat filenames purely as data: - Always include -- before filename lists in git commands. - Use robust quoting and consider null-delimited pipelines for filenames. - Refactor the hook so that it does not assemble command lines from raw filenames where possible.

Severity:

CRITICAL RISK

(9.8)

Command Option Injection (CWE-77) in OpenClaw git pre-commit Hook

CVE-2026-28484

Published:

Mar 5, 2026

Status:

Received

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

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Command Injection / Argument Injection

CWE:

CWE-77

Impact:

Exposure of Sensitive Files in Git History

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Command Injection / Argument Injection

CWE:

CWE-77

Impact:

Exposure of Sensitive Files in Git History

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 Option Injection (CWE-77) in OpenClaw git pre-commit Hook

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

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

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