Git
Heap-based Buffer Overflow in Git
Affected versions of Git have a heap buffer overflow in the three-way merge code (xdiff), which an attacker can trigger through a repository they control. When Git merges a file, it first adds up the size of the merged output, allocates a buffer of that size, and then writes the output into it. That total was kept in a 32-bit signed integer. The conflict-marker-size attribute, which can be set from a committed .gitattributes file, accepts any positive integer, and the markers are written several times for every conflict. A small file with a huge marker size and many separate conflicts can therefore push the total past 4 GiB, so the integer wraps to a small value and Git writes attacker-controlled merge output past the end of a buffer that is too small. At minimum this crashes Git, and because the overflow is large and its contents are largely attacker-controlled, worse heap corruption is possible. Any command that does a textual three-way merge can trigger it, such as git-merge(1), git-rebase(1), git-cherry-pick(1), and git-merge-tree(1). The latter is most likely a target for Git forges, which might use git-merge-tree(1) on the server-side to check mergeability. When the server reads attributes from trees in the repository (for example through attr.tree or --attr-source), any user who can push branches and request that they be merged (for example by opening a pull or merge request) can trigger the overflow without anyone else doing anything, and the data they push is small because the oversized output only appears during the merge. The problem has been patched by computing the size as size_t and checking every addition for overflow, so Git stops with an error instead of overflowing. Servers that cannot upgrade right away can add * conflict-marker-size=7 to each repository's info/attributes as a workaround, which overrides any in-tree .gitattributes, or turn off server-side mergeability checks for untrusted repositories.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.49.1
- >= 2.50.0-rc0, < 2.50.2
- >= 2.51.0-rc0, < 2.51.3
- >= 2.52.0-rc0, < 2.52.1
- >= 2.53.0-rc0, < 2.53.1
- >= 2.54.0-rc0, < 2.54.1
- >= 2.55.0-rc0, < 2.55.1
- >= 2.56.0-rc0, < 2.56.1
Fixed in 2.49.1, 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, 2.56.1
Mitigation
Upgrade to versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, 2.56.1 or above.
Timeline
Days relative to CVE publicationFirst public PoC 11 h after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-105437 (created 11 Nov 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| googlesky/CVE-2026-105437 | 11 Nov 2026 +11 h | 14 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | HackerOne Bug Bounty Report #4044249 | unknown | 14 Nov 2026 |
PoC characteristics
What to hunt for in your logs · from 1 PoC repoPOST" IF PAYLOAD IS NOT NONE ELSE "GET /merge-check
- Ports
- 8080
- Seen in
- 1 repo: googlesky/CVE-2026-105437
- Evidence
- googlesky/CVE-2026-105437/poc/poc.py:121
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/merge-check(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-105437 Git Git exploit attempt"; flow:established,to_server; http.method; content:"POST|22| IF PAYLOAD IS NOT NONE ELSE |22|GET"; http.uri; content:"/merge-check"; reference:url,poc.griffinguard.io/cve/CVE-2026-105437; classtype:web-application-attack; sid:9562324; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: Git Git exploit attempt (CVE-2026-105437)
id: gg-pocmon-cve-2026-105437-9562324
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-105437. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-105437
logsource:
category: webserver
detection:
selection:
cs-method: POST" IF PAYLOAD IS NOT NONE ELSE "GET
cs-uri-stem|contains|all:
- '/merge-check'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.105437