Git 2.56.1 fixes six vulnerabilities, including CVE-2026-111760 code execution during recursive clones of malicious repositories
Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 4 fontes trouxeram em 17/11/2026 00:07; os links antigos trazem para cá.
Fontes: cert.cyber.gouv.fr ↗ helpnetsecurity.com ↗ securityonline.info ↗ thehackernews.com ↗
Git released Git 2.56.1 and backported maintenance releases on 10 November 2026 to fix six vulnerabilities. They allow code execution, arbitrary file writes, memory corruption and information leakage when Git processes malicious repositories or crafted input (helpnetsecurity.com, securityonline.info). The most severe is CVE-2026-111760, an integer-truncation flaw that can lead to remote code execution during a recursive clone (thehackernews.com). The French CERT-FR published advisory CERTFR-2026-AVI-1541 on 16 November, citing the vendor's advisory GHSA-vp2w-7xxj-jvxr of 10 November. It says the flaw is exploitable only with the --recurse-submodules option (cert.cyber.gouv.fr). No in-the-wild exploitation had been reported as of the securityonline.info report, and no threat actor or IOCs appear in any source. GitHub says it has deployed fixes across github.com and its cloud offerings (helpnetsecurity.com).
Entenda a falha
A vulnerabilidade
Git 2.56.1 fixes six flaws. The most severe is CVE-2026-111760, an integer truncation in Git's index handling that can lead to code execution when a victim clones a malicious repository recursively with its submodules. The attacker needs the victim to run a recursive clone (--recurse-submodules) of a repository they control. Securityonline.info gives a CVSS v3 of 8.0 for this CVE, while The Hacker News calls it critical. The other five are CVE-2026-113408 (path traversal in protocol v2 cloning of an empty repository, writing outside the refs directory), CVE-2026-114467 (stack overflow when a tag has more than two GPG signatures), CVE-2026-114469 (out-of-bounds read from a binary patch that expands past 1 GiB), CVE-2026-105437 (heap overflow in large merges) and CVE-2026-114466 (fast-import features that read or write arbitrary files). Fixes are in Git 2.56.1 and the backports 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2; GitHub Enterprise Server is fixed in 3.19.15, 3.20.11, 3.21.9 and 3.22.4.
Como funciona
In a recursive clone, Git checks out the repository and then each submodule, whose .git is a file pointing to its git directory. While handling paths in the index, Git processes an extremely long path. The length is truncated, so the path passes the safety checks under its full name but is written to disk under a shorter name that the attacker can make equal to .git. This lets the attacker replace the submodule's .git file with a symbolic link to a directory holding malicious hooks or configuration. Git then uses that directory, and since hooks are programs Git runs at set points, the attacker's code runs during the clone.
Por que é vulnerável
The root cause is an integer truncation: the length of an index path is cut short after the safety check was done on the full-length name, so the checked name and the written name differ. Git normally refuses to replace a .git directory with a symlink, but in a freshly cloned submodule .git is a file, which makes the swap possible. The fix rejects overly long index paths before their length can be truncated. The articles do not say why it went unnoticed.
Onde está
The articles name no file, function or commit; the only reference is the Git advisory GHSA-vp2w-7xxj-jvxr, and the flaw lies in Git's index path handling.
Como foi descoberta
The articles do not say who found the flaw or how. The Git project released 2.56.1 and the backports on 10 November 2026 and published advisory GHSA-vp2w-7xxj-jvxr, and GitHub published a detailed write-up of the fixes. GitLab assigned CVE-2026-105437. CERT-FR followed on 16 November with CERTFR-2026-AVI-1541, noting the vendor believes only --recurse-submodules use is exploitable. No exploitation in the wild had been reported.
Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 00:22.
Detalhes técnicos
- CVE-2026-111760: an integer truncation in Git's index path handling lets an overly long path pass safety checks under one name and be written under a shorter name. The flaw mainly affects submodules whose .git is a file. An attacker can replace that file with a symlink to attacker-controlled hooks or configuration, so code runs during a recursive clone. The fix rejects overly long index paths before truncation (thehackernews.com, helpnetsecurity.com).
- CVE-2026-113408: protocol v2 cloning of an empty repository did not validate the target of an advertised HEAD symbolic ref. A malicious server could use path-traversal components to write outside the intended refs directory with the files reference backend. Git now validates received reference names and symbolic-reference targets (helpnetsecurity.com).
- CVE-2026-114467: the GPG-signature stripping code assumed at most two signatures. A crafted message with more signatures can overflow a fixed-size stack array, causing memory corruption or crashes. Services that merge on behalf of users are affected (helpnetsecurity.com).
- CVE-2026-114469: binary-patch handling checked only the compressed patch size. A small patch can therefore expand beyond the roughly 1 GiB limit, leading to out-of-bounds reads (helpnetsecurity.com). The source text is truncated here, so further detail is unavailable.
- CVE-2026-105437: a merge memory-size overflow (helpnetsecurity.com).
- CVE-2026-114466: unsafe fast-import stream handling that can read or write arbitrary files (helpnetsecurity.com).
- The securityonline.info report puts the CVSS v3 scores of the set at up to 8.0.
Remediação
- Upgrade to Git 2.56.1, or to the matching backported release in the 2.55 to 2.50 series (helpnetsecurity.com). Both securityonline.info and thehackernews.com advise updating promptly.
- GitHub Enterprise Server administrators should move to 3.19.15, 3.20.11, 3.21.9 or 3.22.4. Patched builds for GitHub Desktop and the GitHub Copilot app are being coordinated, and GitHub Codespaces and GitHub Actions will receive updates (helpnetsecurity.com).
- Until patched, avoid cloning untrusted repositories with --recurse-submodules (cert.cyber.gouv.fr). The helpnetsecurity.com article says the advisory repeats mitigations for environments that cannot update, but its excerpt does not list them.
Relatos divergentes
- Severity: thehackernews.com calls the flaw critical, while securityonline.info gives a CVSS v3 score of up to 8.0 for the set. CERT-FR gives no score. The sources do not say which CVE carries the 8.0.
- Affected and fixed versions: thehackernews.com says the fix is in "Git 2.56.1 and earlier versions", which is ambiguous. helpnetsecurity.com is more specific: 2.56.1 plus backports across 2.55 to 2.50. CERT-FR lists no versions. Treat the helpnetsecurity.com version information as more reliable.
- Exposure: CERT-FR, the most recent source (16 November), relays the vendor's view that exploitation requires --recurse-submodules. The other sources describe the recursive clone scenario without that explicit qualifier.
Linha do tempo
-
CERT-FR: Git vulnerability CVE-2026-111760 allows remote code execution, exploitable only with --recurse-submodules
ler a análise desta fonte ocultar
The French CERT (CERT-FR) published advisory CERTFR-2026-AVI-1541 on a vulnerability in Git that allows remote arbitrary code execution. The advisory says the vendor believes the flaw is exploitable only when the --recurse-submodules option is used, which limits the exposure. The flaw is tracked as CVE-2026-111760 and covered by Git GitHub Security Advisory GHSA-vp2w-7xxj-jvxr of 10 November 2026. The advisory gives no CVSS score, affected or fixed versions, exploitation status, threat actor or IOCs. No web research was performed, so the vendor's own details are not confirmed here.
Remediation
Consult the Git security advisory GHSA-vp2w-7xxj-jvxr for the fixed versions and apply them. Until then, avoid cloning untrusted repositories with --recurse-submodules.
-
Git fixes six vulnerabilities including recursive-clone code execution (CVE-2026-111760)
This article confirms the six CVEs and provides release and deployment details: fixes are shipped in **Git 2.56.1** with backported releases for the 2.55–2.50 series, and **GitHub** reports having deployed fixes across github.com and its cloud offerings. GitHub Enterprise Server administrators are advised to upgrade to versions **3.19.15**, **3.20.11**, **3.21.9** or **3.22.4**; patched builds for GitHub Desktop and the GitHub Copilot app are being coordinated, and GitHub Codespaces and GitHub Actions will receive updates. The advisory also repeats practical mitigations for environments that cannot update immediately. (helpnetsecurity.com)
ler a análise desta fonte ocultar
This article confirms the six CVEs and provides release and deployment details: fixes are shipped in Git 2.56.1 with backported releases for the 2.55–2.50 series, and GitHub reports having deployed fixes across github.com and its cloud offerings. GitHub Enterprise Server administrators are advised to upgrade to versions 3.19.15, 3.20.11, 3.21.9 or 3.22.4; patched builds for GitHub Desktop and the GitHub Copilot app are being coordinated, and GitHub Codespaces and GitHub Actions will receive updates. The advisory also repeats practical mitigations for environments that cannot update immediately. (helpnetsecurity.com)
Git released security updates addressing six vulnerabilities that can allow code execution, arbitrary file writes, memory corruption and information leakage when processing malicious repositories or crafted input. The most severe, CVE-2026-111760, is an integer-truncation bug in Git's index handling that can be abused to replace a submodule's .git file with a symlink to attacker-controlled hooks or configuration, enabling code execution during a recursive clone. Additional flaws include a protocol v2 reference validation bypass (CVE-2026-113408), a GPG-signature stripping stack overflow (CVE-2026-114467), binary-patch expansion leading to out-of-bounds reads (CVE-2026-114469), a merge memory-size overflow (CVE-2026-105437), and unsafe fast-import stream handling that can read or write arbitrary files (CVE-2026-114466). Patches ship in Git 2.56.1 with backports across the 2.55–2.50 series; GitHub reports deployment of fixes across its services and provides upgraded GitHub Enterprise Server builds (see Remediation). (helpnetsecurity.com)
Technical Details
- CVE-2026-111760: integer truncation in Git index path handling allows an overly long path to pass safety checks under one name and be written under a shorter name; an attacker can then replace a submodule's .git file with a symlink that points to attacker-controlled hooks/configuration, enabling execution during recursive clones. The fix rejects overly long index paths before truncation. (helpnetsecurity.com)
- CVE-2026-113408: protocol v2 cloning of an empty repo did not validate the target of an advertised HEAD symbolic ref, allowing a malicious server to use path-traversal components to write outside the intended refs directory when using the files reference backend. Git now validates received reference names and symbolic-reference targets. (helpnetsecurity.com)
- CVE-2026-114467: GPG-signature stripping code assumed at most two signatures; a crafted message with more signatures could overflow a fixed-size stack array, causing memory corruption or crashes (impacting services that merge on behalf of users). (helpnetsecurity.com)
- CVE-2026-114469: binary-patch handling checked only compressed patch size, allowing a small supplied patch to expand beyond the ~1 GiB limit when decoded, causing out-of-bounds reads/crashes. Git now checks declared uncompressed size before processing. (helpnetsecurity.com)
- CVE-2026-105437: merge machinery can overflow a memory-size calculation for very large results (many conflicts combined with large conflict-marker-size), possibly leading to heap corruption during local merges or when services merge untrusted content. (helpnetsecurity.com)
- CVE-2026-114466: git fast-import accepted three unsafe features from input streams; two submodule-rewrite options could read arbitrary files (leaking contents via error messages) and a third could create/append files. Unsafe features are now rejected unless explicitly allowed. GitHub advises enabling them only for trusted stream generators. (helpnetsecurity.com)
Fix Details
- The fixes are released in Git 2.56.1, with backported patched releases in the 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2 series. GitHub has deployed fixes across github.com, GitHub Enterprise Cloud and GitHub Enterprise Cloud with data residency; GitHub Enterprise Server administrators should upgrade to 3.19.15, 3.20.11, 3.21.9 or 3.22.4. Patched Git builds are being coordinated for GitHub Desktop and the GitHub Copilot app; GitHub Codespaces and GitHub Actions will also receive updates. (helpnetsecurity.com)
Remediation
- Install Git 2.56.1 or the patched release for the relevant supported series, and update any software bundling its own copy of Git. For GitHub Enterprise Server, upgrade to the specified patched versions. If immediate updating is impossible: clone only from trusted servers, avoid recursive clones of untrusted repositories, avoid merging untrusted content or tags, and do not process binary patches or fast-import streams from untrusted sources. These mitigations do not replace installing the fixes. Quote from Elijah Newren, GitHub: "If you cannot update immediately, clone only from trusted servers and avoid recursive clones of untrusted repositories..." (helpnetsecurity.com).
-
Git 2.56.1 Patch Fixes Critical Code Execution and Memory Flaws
ler a análise desta fonte ocultar
The Git project released version 2.56.1 and multiple maintenance updates to address six security vulnerabilities. These flaws include remote code execution during recursive clones, path traversal, and memory corruption issues, rated with a CVSS v3 score up to 8.0. While no active exploits have been reported in the wild, the vulnerabilities pose a significant risk given Git's widespread usage across development environments and cloud services. Users are advised to update immediately to mitigate potential attacks.
-
Git vulnerability allows malicious repositories to execute code during recursive clones
ler a análise desta fonte ocultar
A critical flaw in Git, identified as CVE-2026-111760, can enable malicious repositories to run attacker's code on a victim's system during recursive cloning, through exploitation of an integer truncation in Git's handling of long file paths. The vulnerability mainly affects submodules where .git is a file, allowing attackers to replace this with a symbolic link to malicious hooks or configuration folders. The Git project has addressed this issue in Git 2.56.1 and earlier versions, advising users to upgrade promptly. Several other vulnerabilities affecting Git were also fixed in the recent release, including issues with path traversal, memory corruption, and arbitrary file access.