PYPI · JULY 2026 · EARLY WARNING

GitPython Vulnerable to Command Injection: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

CVE-2026-42215GHSA-2F96-G7MH-G2HXGHSA-RPM5-65CW-6HJ4Severity: HIGH

GitPython versions 3.1.47 through 3.1.50-42 appear to be vulnerable to command injection, allowing potential execution of arbitrary commands.

What happened

GitPython, a Python library for interacting with Git repositories, is under investigation for a critical vulnerability (CVE-2026-42215, GHSA-2F96-G7MH-G2HX, GHSA-RPM5-65CW-6HJ4) that allows command injection via a long-option prefix abbreviation bypass. This vulnerability reportedly enables attackers to execute arbitrary commands by exploiting an incomplete fix of a previous issue. Engineers using affected versions (3.1.47 through 3.1.50-42) should monitor for updates and consider implementing version control mechanisms to ensure safe usage of the package. For more detailed information, consult the primary sources.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If GitPython is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats