PYPI · JULY 2026 · EARLY WARNING

GitPython <= 3.1.52: Section-Name Injection Vulnerability Under Investigation

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-3RP5-JJMW-4WV2GHSA-MV93-W799-CJ2WSeverity: HIGH

An early warning has been issued regarding a potential section-name injection vulnerability in GitPython <= 3.1.52, which could allow remote code execution. Users of this package are advised to upgrade.

What happened

Reportedly, a vulnerability in GitPython <= 3.1.52 allows an attacker to inject arbitrary configuration directives through insufficient escaping of section names in the configuration file. This could potentially lead to remote code execution. The issue is currently under investigation with tracked IDs GHSA-3RP5-JJMW-4WV2, GHSA-MV93-W799-CJ2W, and GHSA-V87R-6Q3F-2J67. To assess your exposure, check if your projects or dependencies include GitPython <= 3.1.52. It is recommended to upgrade to a version greater than 3.1.52 to mitigate the risk. For more details, 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