Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102829 Overview
CVE-2026-102829 is a command injection vulnerability in the @simple-git/argv-parser package used by simple-git, a Node.js interface for executing Git commands. The parseEnv function omits the VISUAL environment variable from GitEnvKeys, causing prepareEnv to drop the value before vulnerabilityCheck can classify it as allowUnsafeEditor. Applications that forward attacker-controlled environment values can allow Git to invoke an attacker-selected editor during operations like commit amendment or interactive rebase. The executable runs with the privileges of the Node.js process. The issue is fixed in @simple-git/argv-parser version 2.0.1.
Critical Impact
Attackers who influence the VISUAL environment variable can execute arbitrary binaries with the privileges of the Node.js process during Git editor-invoking operations.
Affected Products
- simple-git Node.js library consuming @simple-git/argv-parser
- @simple-git/argv-parser versions prior to 2.0.1
- Node.js applications forwarding attacker-influenced environment variables to simple-git
Discovery Timeline
- 2026-09-29 - CVE-2026-102829 published to NVD
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-102829
Vulnerability Analysis
The vulnerability [CWE-78] resides in the environment variable filtering logic of @simple-git/argv-parser. The parseEnv function maintains a GitEnvKeys map that pairs sensitive environment variables with their corresponding vulnerability categories. The map covered pager, prefix, and ssh_askpass but omitted visual.
Without visual in GitEnvKeys, prepareEnv strips the VISUAL value from the forwarded environment before vulnerabilityCheck evaluates it. The safety check never runs against the editor category, allowing the variable to pass through unrestricted paths.
Git consults VISUAL when invoking an editor for operations such as git commit --amend or git rebase -i. When higher-priority editor settings like GIT_EDITOR are unset and Git's terminal prerequisites are met, Git executes the binary named by VISUAL.
Root Cause
The root cause is an incomplete allowlist of tracked environment variables in the argv-parser. Because visual was not mapped to allowUnsafeEditor, the parser could not classify it as unsafe, and the sanitization pipeline failed to enforce editor safety policy.
Attack Vector
Exploitation requires a consuming application to forward attacker-influenced environment values to simple-git and then trigger a Git operation that invokes an editor. The attacker sets VISUAL to an arbitrary executable path. When Git spawns the editor, the executable runs with the privileges of the Node.js process.
'pager': 'allowUnsafePager',
'prefix': 'allowUnsafeConfigPaths',
'ssh_askpass': 'allowUnsafeAskPass',
+ 'visual': 'allowUnsafeEditor',
} as const satisfies Record<string, VulnerabilityCategory>;
type GitEnv = Record<string, string> & {
Source: GitHub Commit 68874c2
The patch adds visual to the tracked environment variables map, binding it to the allowUnsafeEditor vulnerability category so vulnerabilityCheck can evaluate and block unsafe editor values.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-102829
Indicators of Compromise
- Node.js processes spawning unexpected child processes during Git operations such as git commit --amend, git rebase -i, or git tag -a.
- Presence of VISUAL environment values pointing to non-standard editor binaries or shell one-liners within Node.js process environments.
- Package manifests (package-lock.json, yarn.lock, pnpm-lock.yaml) pinning @simple-git/argv-parser versions below 2.0.1.
Detection Strategies
- Perform software composition analysis to identify simple-git dependencies resolving to @simple-git/argv-parser versions prior to 2.0.1.
- Instrument application logs to capture environment variables forwarded into simple-git API calls, and alert on user-controlled values in editor-related keys.
- Correlate Git subprocess execution with the parent Node.js process command line to detect editor invocations that deviate from baseline behavior.
Monitoring Recommendations
- Monitor process creation telemetry for Node.js parents launching shells or interpreters through Git child processes.
- Track outbound network connections initiated by processes spawned as children of Git during editor-invoking operations.
- Audit CI/CD job logs where simple-git is used, focusing on jobs that accept environment overrides from external triggers.
How to Mitigate CVE-2026-102829
Immediate Actions Required
- Upgrade @simple-git/argv-parser to version 2.0.1 or later across all applications consuming simple-git.
- Audit application code that constructs environment objects passed to simple-git, and strip VISUAL, EDITOR, and GIT_EDITOR unless explicitly required.
- Rebuild and redeploy container images and serverless functions that bundle the vulnerable dependency.
Patch Information
The fix is available in @simple-git/argv-parser@2.0.1. Details are published in the GitHub Security Advisory GHSA-v5rq-49vh-5v5c, the Pull Request #1201, and the release notes for @simple-git/argv-parser 2.0.1.
Workarounds
- Explicitly set GIT_EDITOR to a trusted binary before invoking simple-git, since Git prioritizes GIT_EDITOR over VISUAL.
- Sanitize the environment passed to simple-git by allowlisting only required variables and removing VISUAL from user-controlled inputs.
- Run Node.js processes that execute Git operations under the least privilege necessary to limit the impact of editor invocation.
# Upgrade the vulnerable package
npm install @simple-git/argv-parser@^2.0.1
# Verify installed version
npm ls @simple-git/argv-parser
# Sanitize environment before invoking simple-git
unset VISUAL
export GIT_EDITOR=/usr/bin/true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

