Git · GitLab · published 2026-11-10

CVE-2026-105437Heap-based Buffer Overflow in Git

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-105437 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 35% of all CVEs. This GitLab vulnerability: CVSS 7.5 (v3.1), a successful attack gives total control of the component. Fixed upstream in GitLab 19.5.4, 19.4.6, 19.3.8; Debian, Ubuntu and Red Hat Enterprise Linux still have unfixed releases. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in GitLab 19.5.4, 19.4.6, 19.3.8.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixiegitNo fix yet
12 bookwormgitNo fix yet
Ubuntu26.04 LTSgitNo fix yet
24.04 LTSgitNo fix yet
22.04 LTSgitNo fix yet
Red Hat Enterprise LinuxRHEL 10gitNo fix yet
RHEL 9gitNo fix yet
RHEL 8gitNo fix yet
RHEL 7gitNo fix yet
RHEL 6gitNo fix yet

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.5.4, 19.4.6, 19.3.8

    Upgrade to 19.5.419.4.619.3.8

    Why: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (35th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →