Critical [CVE-2026-78676] GitPython before 3.1.59 Remote Code Execution via Config Injection
This critical-severity Red Hat Linux advisory covers CVE-2026-78676 affecting Exploit Intelligence, Migration Toolkit for Applications 8, Red Hat AI Inference Server.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
Case for AC:H (8.1): the trigger needs two things the attacker does not straightforwardly own: (1) a crafted multi-line quoted value must already sit DORMANT in.git/config — the guarded set_value() path will not put it there; it must arrive via _read() of a file the attacker influenced but does not directly write; and (2) a SUBSEQUENT, UNRELATED GitPython config WRITE must fire to re-serialize and corrupt it — and that write is performed by the victim application on its own schedule, not by the attacker. "Prepare the target environment" + "conditions beyond the attacker's control" is the textbook AC:H definition; step (2) in particular fits it.
Red Hat severity: Critical — CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-88.
Affected products named by the advisory: Exploit Intelligence; Migration Toolkit for Applications 8; Red Hat AI Inference Server; Red Hat Ansible Automation Platform 2; and 5 more.
- < 3.1.59
Official advisory · high-confidence parse· fetched 57 minutes ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 57 minutes ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · high-confidence parse· fetched 57 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.