Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

GitPython in Docker images can run malicious code

published 10 days ago
Summary

Versions of GitPython older than 3.1.59 that are included in the docker hardened images for git-mcp and mlflow may mishandle multi-line configuration files. A specially crafted config file can be turned into active Git settings, such as a hook path, that cause the system to execute arbitrary code when Git runs. Update GitPython to version 3.1.59 or newer in those images to stop this behavior.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.24 docker hardened images git-mcp All versions
Docker Hardened Images:Debian:13 docker hardened images git-mcp All versions
Docker Hardened Images:Debian:13 docker hardened images mlflow All versions
Original advisory text
GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting…
GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation.
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker full control (estimated)
Severity
9.9 Critical
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta