CVE-2026-73625 in GitPython
Summary
by MITRE • 08/13/2026
GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard that can be bypassed by smuggling git options inside single-character kwarg values. Attackers can supply crafted option dictionaries to clone_from, fetch, pull, push, ls_remote, iter_commits, blame, or archive methods to execute arbitrary OS commands via the --upload-pack parameter.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 08/13/2026
This vulnerability affects GitPython versions prior to 3154 and represents a critical remote code execution flaw stemming from inadequate input validation within the check_unsafe_options guard mechanism. The technical implementation flaw resides in how the library processes keyword arguments during git operations, specifically allowing attackers to smuggle malicious git options through single-character kwarg values that bypass the intended security checks.
The vulnerability operates through a sophisticated smuggling technique where attackers craft option dictionaries containing specially formatted single-character keys that contain dangerous git command parameters. When these crafted parameters reach methods such as clone_from, fetch, pull, push, ls_remote, iter_commits, blame, or archive, the unsafe options validation fails to properly sanitize the input, allowing arbitrary OS command execution via the --upload-pack parameter. This represents a classic bypass of defensive mechanisms that rely on string-based validation rather than comprehensive parameter analysis.
The operational impact of this vulnerability extends beyond simple code execution to encompass complete system compromise when attackers can influence git operations through vulnerable applications or services using GitPython. The attack vector typically involves scenarios where user input is passed directly to git methods without proper sanitization, making web applications, CI/CD pipelines, and automated systems particularly susceptible.
Security controls should focus on implementing comprehensive input validation that examines all parameter combinations rather than relying solely on string-based sanitization. Organizations should immediately upgrade to GitPython version 3154 or later where the vulnerability has been addressed through enhanced option validation mechanisms. Additional mitigations include implementing strict input filtering at application boundaries, employing least-privilege principles for git operations, and monitoring for suspicious command execution patterns.
This vulnerability aligns with CWE-78 which describes improper neutralization of special elements used in OS commands, and maps to ATT&CK technique T1059.003 for command and scripting interpreter. The bypass mechanism demonstrates how attackers can circumvent security controls through clever input manipulation, highlighting the importance of robust parameter validation rather than simple string sanitization approaches. Organizations should conduct comprehensive code reviews to identify similar patterns in other libraries and applications that may be vulnerable to analogous smuggling attacks.