Git releases fixes for six security vulnerabilities, including code execution risks
- Severity
- High
- Sources
- 1
What happened
Git 2.56.1 fixes six CVEs (CVE-2026-111760, CVE-2026-113408, CVE-2026-114467, CVE-2026-114469, CVE-2026-105437, CVE-2026-114466), with backports to 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. Issues include integer truncation in index path handling enabling code execution during recursive clones, unvalidated protocol v2 symref targets enabling path traversal, stack overflow on messages with more than two GPG signatures, binary patch size checks bypassed by compressed expansion, overflow in merge buffer sizing, and fast-import features that read or write files. GitHub Enterprise Server is patched in 3.19.15, 3.20.11, 3.21.9 and 3.22.4. Upgrade Git and bundled copies; until then avoid recursive clones and merges of untrusted content, and restrict fast-import to trusted streams.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Update Git to version 2.56.1, or the patched release for your maintenance series.
- Update any applications that bundle their own copy of Git.
- GitHub Enterprise Server administrators should upgrade to 3.19.15, 3.20.11, 3.21.9 or 3.22.4 as soon as possible.
- If you cannot update immediately, avoid recursive clones of untrusted repositories and avoid merging untrusted content or processing untrusted binary patches or fast-import streams.
Written by AI from the sources, checked against them
Full story timeline · 1 update
- Tue 10 NovemberGit security vulnerabilities announcedGitHub Security Blog
Who reported · 1 outlet
Who and what is in it
Products