nday
CVE-2026-105437

Heap-based Buffer Overflow in Git

Git / Git

公開から 1 日後に技術解析が確認されています。nday はまだ修正の根拠を取得していません。修正がないという意味ではありません。4 つの PoC ソースのいずれにも未掲載です。CISA KEV には現時点で未掲載です。

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

buffer overflow / out-of-bounds write
CWE-122, stated by the CNA GitLab、NVD, republishing [email protected]
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA GitLab
no authentication required
PR:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA GitLab
現在の段階
ANA
公開日時
CVSS 基本値
7.5 HIGH v3.1

ライフサイクル

横軸は UTC。点=分単位、幅広の帯=日付のみ、白抜き=不明または推定。
日時不明
DIS公開
11-10T18:34Z
PAT修正
記録なし
ANA解析
11-11T14:24Z
POCPoC
記録なし
ITW悪用
記録なし
KEVKEV
記録なし

概要

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA GitLab.

イベント履歴

+DIS公開

GitLab が CVE レコードを公開。CVSS 基本値 7.5(重要)。CISA の SSVC 評価では悪用状況(Exploitation)が poc。

出典 cvelist · nday が に一括取り込み · 生データ
{
  "id": 4199,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-105437",
  "occurred_at": "2026-11-10T18:34:09.369Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7.5,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-11-16T18:22:06.298762Z",
      "automatable": "no",
      "exploitation": "poc",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-10T18:34:09.369Z",
    "assigner_short_name": "GitLab"
  }
}
+ANA技術解析

oss-security メーリングリストへの投稿:「git: v2.56.1 and older maintenance release fixes for six vulnerabilitie」。

出典 osssec 2026/q4/659 · nday が にリアルタイムで観測 · 生データ
{
  "id": 496439,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/659",
  "occurred_at": "2026-11-11T14:24:58Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/659",
  "detail": {
    "list": "oss-security",
    "author": "Johannes Schindelin",
    "subject": "git: v2.56.1 and older maintenance release fixes for six vulnerabilitie",
    "is_reply": false
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

研究者の投稿

過去 7 日間に 0 人の研究者が言及

リストの研究者が X でこの CVE に触れた投稿です。原文のまま表示し、nday は検証していません。

リストの研究者が X でこの CVE に触れた投稿は、まだ収集していません。

Discussion

0 comments

No comments yet.