boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-105437

Git Git — Heap-based Buffer Overflow in Git
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   N   H   N   R  U  H  H  H    7.5   .0040   34.9     —
AFFECTED
  Product  Versions     Fixed
  Git      unspecified  —
TIMELINE
  Oct 5   Reserved by GitLab
  Nov 10  Published (CNA: GitLab)
  Nov 15  EXPLOIT PUBLISHED — CVE-2026-105437 (Git). Public exploit reference added.
  Nov 16  EXPLOIT PUBLISHED — CVE-2026-105437 (Git). Public exploit reference added.
CWE-122 · CNA: GitLab · CVSS v3.1 · 3 references · NVD status: Deferred

Description

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.

Lifecycle

Complete event history — 4 events, chronological
DateEventDetail
October 5, 2026ReservedReserved by GitLab
November 10, 2026PublishedPublished (CNA: GitLab)
November 15, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-105437 (Git). Public exploit reference added.
November 16, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-105437 (Git). Public exploit reference added.

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
GitGit———

Weaknesses

CWE-122

References (3)

Related

Authoritative record: CVE-2026-105437 at cve.org

Vendors: git

Weaknesses: CWE-122

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-105437 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.