Skip to main content
VulnerabilityPublished

CVE-2026-105437: git security update

Affects gitSource GCVE Database

0
Compare
Authoritative record:CVE-2026-105437· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.33.0-23.oe2203sp4 soon.

Data as of 19 Nov 2026, 03:50 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.17.5
Patch
Available – fixed in 2.33.0-23.oe2203sp4
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade git to 2.33.0-23.oe2203sp4.

Affected software

ProductAffectedFixed in
openEuler 22.03-LTS-SP4gitpkg:rpm/openEuler/git&distro=openEuler-22.03-LTS-SP4Other threatsAffected
  • <2.33.0-23.oe2203sp4
Fixed in
  • 2.33.0-23.oe2203sp4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Git version 2.33.0-23.oe2203sp4 and later; upgrading to this version or newer fully mitigates the vulnerability. For servers that cannot upgrade immediately, adding conflict-marker-size=7 to each repository's info/attributes file overrides any in-tree .gitattributes settings and mitigates the overflow risk. Alternatively, disabling server-side mergeability checks for untrusted repositories can prevent exploitation. No other actions are required if the patch is applied.

Description

A heap buffer overflow vulnerability exists in Git's three-way merge code (xdiff) due to improper handling of the conflict-marker-size attribute, allowing an attacker controlling a repository to cause an integer overflow and write beyond allocated buffer boundaries. This can lead to crashes or heap corruption. The flaw affects Git versions prior to 2.33.0-23.oe2203sp4 and is triggered by commands performing textual three-way merges, including git-merge, git-rebase, git-cherry-pick, and git-merge-tree. The issue has been patched by changing the size calculation to use size_t and adding overflow checks. Workarounds for servers unable to upgrade immediately include setting conflict-marker-size=7 in repository info/attributes or disabling server-side mergeability checks for untrusted repositories.

References

Community reviews

Loading reviews…