PYPI · AUGUST 2026 · EARLY WARNING

GitPython Vulnerability: Arbitrary File Overwrites Reported

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-4GMW-GG2M-W46PSeverity: HIGH

A vulnerability in GitPython reportedly allows arbitrary file overwrites. Users of affected versions should assess their exposure.

What happened

An early warning has been issued regarding a vulnerability in the GitPython package. The issue stems from unguarded git read-tree option forwarding in the IndexFile.from_tree, IndexFile.reset, and IndexFile.merge_tree methods, which could enable arbitrary file overwrites. This vulnerability affects multiple versions of GitPython, from the initial release up to version 3.1.51. It is recommended to upgrade to a version that includes a fix for this vulnerability, if available, and to monitor for any potential unauthorized file modifications. The full list of affected versions can be found in the provided threat data. For the latest 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