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.54.1-1.oe2403sp4 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.54.1-1.oe2403sp4
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.54.1-1.oe2403sp4.

Affected software

ProductAffectedFixed in
openEuler 24.03-LTS-SP4gitpkg:rpm/openEuler/git&distro=openEuler-24.03-LTS-SP4Other threatsAffected
  • <2.54.1-1.oe2403sp4
Fixed in
  • 2.54.1-1.oe2403sp4

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.54.1-1.oe2403sp4 and later; upgrading to this version or newer fully mitigates the vulnerability. For servers unable to upgrade immediately, setting conflict-marker-size=7 in each repository's info/attributes file overrides any in-tree .gitattributes and prevents the overflow. Alternatively, disabling server-side mergeability checks for untrusted repositories can mitigate risk. Users should avoid merging or cloning from untrusted repositories until patched.

Description

Git versions prior to 2.54.1-1.oe2403sp4 contain a heap buffer overflow vulnerability in the three-way merge code triggered by specially crafted repository data. This overflow occurs due to a 32-bit signed integer wrap when calculating the size of merged output with large conflict-marker-size attributes, potentially leading to heap corruption or crashes. The flaw can be exploited by an attacker controlling a repository, affecting commands that perform textual three-way merges such as git-merge, git-rebase, git-cherry-pick, and git-merge-tree. A patch is available that fixes the issue by using size_t for size calculations and checking for overflow. Workarounds include limiting conflict-marker-size or disabling server-side mergeability checks for untrusted repositories.

References

Community reviews

Loading reviews…