The Git project has released a series of security updates addressing six distinct vulnerabilities that could allow for unauthorized code execution, memory corruption, or arbitrary file manipulation. These flaws are triggered when the software processes malicious repositories or specially crafted inputs. The patches are included in Git version 2.56.1, with backported fixes available for the 2.50.2 through 2.55.1 release series.
The most severe issue, tracked as CVE-2026-111760, involves an integer truncation vulnerability within Git's index handling. An attacker can exploit this by providing an excessively long file path that passes initial safety checks but is subsequently shortened. This discrepancy allows the replacement of a submodule’s .git file with a symbolic link, which can then be used to execute arbitrary code during a recursive clone operation. The update resolves this by rejecting overly long index paths before truncation can occur.
A second vulnerability, CVE-2026-113408, concerns the v2 protocol. When cloning an empty repository, Git failed to properly validate the target of a HEAD symbolic reference advertised by the server. This allowed a malicious server to employ path-traversal techniques to write files outside of the intended reference directory during a branch update. The fix ensures that all reference names and symbolic-reference targets are strictly validated.
Memory corruption risks were identified in two separate areas. CVE-2026-114467 involves the stripping of GPG signatures, where the code incorrectly assumed a message would contain no more than two signatures. A crafted message exceeding this limit can overflow a fixed-size stack array, potentially crashing the system or causing corruption, a scenario particularly relevant to hosting services that perform automated merges. Additionally, CVE-2026-105437 affects the merge machinery, where an integer overflow during memory-size calculations can lead to the allocation of an undersized buffer, resulting in heap memory corruption when processing large numbers of conflicts.
Binary patches are the subject of CVE-2026-114469. Previously, Git only verified the size of the patch as supplied, failing to account for the size of the data after expansion. This allowed a small patch to trigger an out-of-bounds read and a crash upon decoding. The software now validates the declared uncompressed size before processing the patch. Finally, CVE-2026-114466 addresses security gaps in git fast-import, where three features were found to lack necessary safeguards when handling untrusted input streams. These features could be leveraged to read arbitrary files or create and append to files on the host system. These actions are now rejected by default unless the caller explicitly authorizes the use of unsafe features.
GitHub has confirmed that it has deployed these fixes across its infrastructure, including GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Cloud with data residency. Administrators of GitHub Enterprise Server are urged to upgrade to versions 3.19.15, 3.20.11, 3.21.9, or 3.22.4 to mitigate these risks. Updates are also being coordinated for GitHub Desktop, GitHub Copilot, GitHub Codespaces, and GitHub Actions.
Users and administrators are advised to update their Git installations immediately, including any software that bundles its own copy of the Git binary. For those unable to apply the patches right away, security guidance suggests limiting cloning to trusted servers, avoiding recursive clones of untrusted repositories, and refraining from merging untrusted tags or processing binary patches and fast-import streams from unknown sources. These measures are considered temporary workarounds and do not substitute for applying the official security patches.





