PYPI · AUGUST 2026 · EARLY WARNING

GitPython Vulnerability: Arbitrary File Overwrite and Read Risk

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.

GHSA-3F7W-8RR8-F37FGHSA-956X-8GVW-WG5VSeverity: HIGH

An early warning has been issued for a high severity vulnerability in GitPython that could allow arbitrary file overwrite and read through unguarded git option forwarding in IndexFile.checkout() and TagReference.create(). This vulnerability affects all versions from 0.1.7 to 3.1.51.

What happened

GitPython, a Python library for interacting with Git repositories, appears to have a vulnerability that enables arbitrary file overwrite and read. This is due to unguarded git option forwarding in the IndexFile.checkout() and TagReference.create() methods. The vulnerability could allow an attacker to overwrite and read files with repository-controlled content. It is recommended to upgrade to a version of GitPython that includes the fix for this vulnerability, or apply the patch if available. The affected versions range from 0.1.7 to 3.1.51. For more detailed information, please 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