Field noteNov 16, 20265 min read1 source

Git for Windows 2.56.1 follows the Brotli fix with six additional security fixes

In one minute

Git for Windows 2.56.1 addresses six security vulnerabilities, including flaws that can enable code execution through recursive clones or corrupt files and memory during repository operations. Teams using Git for Windows should update and check whether automated clone, merge, or fast-import workflows process repositories they do not fully control.

What happened

Git for Windows’ release notes identify version 2.56.1 as addressing six security issues: CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467, CVE-2026-114469, and CVE-2026-105437. The notes describe the update relative to Git for Windows v2.56.0(4), dated October 26, 2026, and say the release includes Git v2.56.1. The release notes give November 10, 2026 as the latest update date for the notes.

The most direct code-execution risk concerns recursive clones. An attacker-controlled repository could exploit a Git bug to cause a gitfile used for submodules to be overwritten with a symbolic link. That link could point to a directory containing malicious configuration or hooks, including attacker-specified code. Another issue involves a server advertising an unborn HEAD containing path-traversal characters; with the files ref backend, ref-updating actions could then write to unintended files.

Three other fixes address memory-safety problems in repository operations. Git’s removal of GPG signatures from commit messages accounted for only two signatures; a message with more could cause stack memory corruption. A large binary patch could evade Git’s approximate 1 GiB patch-size check because its compressed input is smaller than the file it describes, then crash Git with an out-of-bounds read when expanded. Separately, a calculation for merge-result buffer size could overflow on very large merges involving many conflicts and a large conflict-marker size, leaving an undersized buffer and causing out-of-bounds writes.

The sixth issue affects git fast-import. Some options introduced after export-marks also allowed reads from arbitrary paths. The release notes say rewrite-submodules-to, rewrite-submodules-from, and export-pack-edges are now disallowed by default, following the earlier restriction on export-marks. That change is a default hardening measure: workflows depending on those features need to establish that their configuration still behaves as intended after the update.

The release combines fixes that arise at different points in normal Git use. A recursive clone can process submodules supplied by a repository; a merge can consume tags and conflict-heavy histories; and import or patch workflows can handle content created elsewhere. The release notes do not present these as one attack chain. Instead, they identify distinct conditions under which crafted repositories, server advertisements, commit messages, tags, or patches may lead to unintended writes, code execution, or memory corruption.

What the archive adds

New Runtime’s earlier coverage of Git for Windows 2.56.0(3) on 2026-10-24 treated that release as a Windows-specific security update. This is a new event: version 2.56.1 adds six more security fixes after the subsequent Brotli fix in 2.56.0(4).

Earlier coverage also tracked the Brotli vulnerability and its fixes on 2026-10-24 and public proof-of-concept exploits and an attempted in-the-wild exploitation on 2026-10-27. Those reports concern CVE-2026-111497, rather than the six CVEs addressed here, so they provide context for the update sequence rather than evidence about exploitation of these newly listed issues.

Trend signal

This release does not yet fit a pattern New Runtime tracks. It is a concrete set of fixes in a widely used version-control tool, but the release alone does not establish a broader shift in agent security architecture or how teams govern agent runtimes.

Why now

The release follows Git for Windows v2.56.0(4), which the notes date to October 26, and the separate v2.56.0(3) Brotli fix. The sequence matters for Windows development environments that rely on Git: teams should distinguish the earlier Brotli remediation from the six additional issues addressed in 2.56.1 rather than assume the previous update covered them.

Why it matters

Git is often a trusted part of development automation, and these vulnerabilities touch operations that may run in CI, repository hosting, or developer workstations. In particular, recursive cloning and merges can involve repository content originating outside a team’s direct control. A compromised repository or crafted input could turn routine source-management work into code execution, unintended file writes, crashes, or memory corruption.

The release makes updating relevant for teams that use Git for Windows, especially where automation clones external repositories or performs merges and fast-import operations. Security teams should also consider whether repository processing is isolated and whether automated workflows can write beyond their intended workspace. A practical review should include build jobs that recursively clone dependencies, automation that imports repository history, and services that merge contributor-controlled branches or tags. The release notes do not establish the exposure of any particular organization, so these are review priorities rather than claims of active compromise.

Limits and uncertainty

The release notes describe the vulnerability mechanics and fixes, but do not establish that any of the six issues have been exploited in the wild. They also do not quantify how many installations or workflows are affected. Exposure depends on whether a team uses Git for Windows and whether its workflows encounter the relevant repository inputs and operations. The notes describe a release history maintained on a moving branch, so teams should consult the current release notes and linked advisories before making deployment decisions. This note does not independently test the fixes or assess exploitability in a particular Windows environment.

Reader takeaway

For teams using Git for Windows, move to v2.56.1 and treat external repositories processed by recursive clone, merge, or fast-import workflows as security-sensitive inputs. The Brotli fix in an earlier release is separate: this update addresses six additional CVEs.

Evidence / sources

  1. 1github.com/git-for-windows/build-extra/blob/main/ReleaseNotes.md
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicSecurityExplore the security topic hub.
  2. 02archiveField NotesOpen the latest editorial analysis.
  3. 03sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract