Git fixes six flaws, including one that lets a malicious repository run code when you clone it with submodules. Update to 2.56.1
The Git project released fixes on 10 Nov 2026 for six vulnerabilities. The worst, CVE-2026-111760, can let a malicious repository run an attacker's code on the machine that clones it recursively. This matters for developers, CI servers and coding agents that clone repositories on their own. What is fixed, what to update and what to avoid.
Updated 10 Nov 2026: see what changedHow urgent
Plan this week
Who is affected
Anyone running Git older than 2.56.1 (or the patched release of an older series: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, 2.50.2), and apps that bundle their own copy of Git. This includes developer laptops, CI runners, containers and servers that clone repositories on behalf of people or AI agents. No source we read says the flaws have been used in real attacks, and we found no severity scores
What to do
Update Git to 2.56.1 or the patched release of your series, on laptops, CI runners, build containers and agent sandboxes, and update apps that bundle Git. Until then, clone only from servers you trust and avoid recursive clones of repositories you do not trust
Published 10 Nov 2026 · Sources last checked 10 Nov 2026No. 71 / 87
Updates, follow-ups and corrections
- Update · 10 Nov 2026. First version of the story, based on GitHub's security write-up and a press report (The Hacker News), both read in a browser on 10 Nov 2026. We did not read the Git project's own release announcement.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
The Git project released new versions to fix six security vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary, according to GitHub's write-up. The fixes are in Git 2.56.1, with matching fixes for older series: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. GitHub recommends updating to 2.56.1 or the patched release of your series, and updating any application that bundles Git.
The one that matters most
CVE-2026-111760 can let a malicious repository run code on the computer that clones it. Git checks file paths before writing them, but an integer truncation in how it handles its index means an extremely long path can pass the check under one name and then be written under a shorter one. An attacker can use that to replace a submodule's .git file with a symbolic link to a folder holding malicious configuration or hooks. When Git then uses that folder, it can run the attacker's code during a recursive clone, which is a clone that also downloads submodules. The fix rejects extremely long paths before the length is truncated.
The other five
- CVE-2026-113408: when cloning an empty repository over Git protocol v2, a malicious server can send a branch name with path-traversal parts, and a later update can write outside the intended folder.
- CVE-2026-114467: merging a tag that carries more than two GPG signatures can corrupt memory.
- CVE-2026-114469: applying a crafted binary patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary can read memory out of bounds.
- CVE-2026-105437: a very large merge with many conflicts can corrupt memory. GitLab assigned this one, per The Hacker News.
- CVE-2026-114466: three
git fast-importfeatures could read or write files outside the repository when fed from an untrusted stream. They are now rejected unless the caller turns on--allow-unsafe-features.
Who should care
Anyone who clones repositories they did not write. That includes developers, and also servers and tools that clone on their own: CI runners, build containers, deployment tools and AI coding agents. They often run a bundled or older Git and may clone whatever they are pointed at.
What GitHub is doing
GitHub says it has deployed fixes on github.com, GitHub Enterprise Cloud and GitHub Enterprise Cloud with data residency. GitHub Enterprise Server fixes are in versions 3.19.15, 3.20.11, 3.21.9 and 3.22.4. Fixed versions of GitHub Desktop and the GitHub Copilot app are being prepared, and Codespaces and Actions will also receive patched Git. The Hacker News reports that Git for Windows had not yet released a version based on 2.56.1 on 10 Nov.
What to do
- Update Git to 2.56.1, or the patched release of your series, from your operating system or Git distributor. Check with
git --version. - Update the places that clone for you: CI runners, build and agent containers (rebuild images that install Git), and apps that ship their own copy of Git.
- If you cannot update yet, GitHub's advice: clone only from servers you trust, avoid recursive clones of repositories you do not trust, do not merge content or tags you do not trust, and do not process binary patches or fast-import streams from untrusted sources.
- If you use Git for Windows, GitHub Desktop or the Copilot app, watch for their fixed releases.
- Let agents clone only repositories you chose. This is our advice, not GitHub's: an agent that follows a link and clones whatever it finds takes on this risk.
What we could not confirm
We read GitHub's security write-up and one press report, not the Git project's own release announcement. We did not find severity scores, and no source we read says any of these flaws has been used in a real attack. We have not tested them ourselves.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- GitHub Blog, Git security vulnerabilities announced (10 Nov 2026; read directly in a browser) (opens in a new tab)
- The Hacker News, Git Patches Flaw That Lets Malicious Repositories Execute Code During Recursive Clones (10 Nov 2026; read directly in a browser) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.