Skip to content

Git vulnerability rated critical by CERT-In; developers told to update to 2.56.1

CERT-In has rated six newly patched Git flaws critical, warning that a booby-trapped repository could run an attacker's code. Fixed releases run from 2.50.2 to 2.56.1.

Lines of colourful program code on a computer monitor, shot in shallow focus

India’s national cyber security agency has rated a set of freshly patched flaws in Git critical, warning that a booby-trapped code repository could hand control of a developer’s computer to an attacker. CERT-In published the Git vulnerability note, CIVN-2026-0552, on Monday, 16 November, and asked individuals and organisations still on older builds to move to the fixed releases.

Git is the version-control tool that keeps a record of every change made to a program’s source code. Students, freelancers and company engineering teams all lean on it, often without opening it directly, because code editors and hosting services run it in the background.

The safe releases are 2.56.1, 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. Any older build in those seven lines is exposed, according to the CERT-In vulnerability note, which lists six CVE numbers.

What the six flaws do

The Git project shipped the fixes on Tuesday, 10 November, and GitHub, which CERT-In cites as the vendor, set out each problem. The flaw behind CERT-In’s code-execution warning lets a hostile repository sneak an extremely long file path past Git’s safety checks. During a recursive clone, which also fetches submodules, that path can swap in hooks or settings that then run the attacker’s code.

A second bug lets a rogue server, when someone clones an empty repository, plant a branch name that lets a later update write files outside the folder where Git keeps its references. Three more can crash Git or scramble its memory: a tag carrying more than two signatures, a merge whose output is too large to size safely, and a compressed binary patch that swells past the roughly 1 GiB limit. The sixth left three fast-import options able to read or write files beyond the repository.

How to stay safe

Updating is the fix. Typing git –version in a terminal shows the installed release, and anything below the patched number for its line should be replaced through the operating system or the Git installer. Apps that ship with a built-in Git need the update as well. GitHub said it had already patched its own website and released GitHub Enterprise Server 3.19.15, 3.20.11, 3.21.9 and 3.22.4 for companies that host their own code.

Where an update must wait, GitHub advised users to clone from servers they trust and to keep unknown tags, binary patches and fast-import input away from Git, while stressing that these steps are no substitute for the patch. Patched Git is also due in GitHub Desktop, Codespaces and Actions, the company said.

Representative image. Photo: Markus Spiske / CC0, via Wikimedia Commons

The Scope Briefing, in your inbox

Five stories that matter, every morning — curated and verified by our editors.