Skip to content
High 7.5

Gitの3方向マージ処理に脆弱性、細工したリポジトリで不正な書き込みが起きるおそれ

CVE-2026-105437 First seen on SecPulse

Summary

Gitのテキストの3方向マージ処理(xdiff)にヒープバッファオーバーフローの脆弱性(CVE-2026-105437)が見つかりました。細工したリポジトリを使うと、Gitが異常終了するほか、ヒープ領域が壊れるおそれもあります。2.49.1、2.50.2、2.51.3、2.52.1、2.53.1、2.54.1、2.55.1、2.56.1より前の版が影響を受けるため、修正版への更新を急いでください。

AI summary

Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.

Gitのテキストの3方向マージ処理(xdiff)にヒープバッファオーバーフローの脆弱性(CVE-2026-105437)が見つかりました。細工したリポジトリを使うと、Gitが異常終了するほか、ヒープ領域が壊れるおそれもあります。2.49.1、2.50.2、2.51.3、2.52.1、2.53.1、2.54.1、2.55.1、2.56.1より前の版が影響を受けるため、修正版への更新を急いでください。

Affected packages

PackageAffected → Fixed
GitGit
< 2.49.1→ 2.49.1
≥ 2.50.0-rc0, < 2.50.2→ 2.50.2
≥ 2.51.0-rc0, < 2.51.3→ 2.51.3
≥ 2.52.0-rc0, < 2.52.1→ 2.52.1
≥ 2.53.0-rc0, < 2.53.1→ 2.53.1
≥ 2.54.0-rc0, < 2.54.1→ 2.54.1
≥ 2.55.0-rc0, < 2.55.1→ 2.55.1
≥ 2.56.0-rc0, < 2.56.1→ 2.56.1

Fix status by distribution

Records published by each distribution for this CVE. Fixed versions differ by release; check each link.

Original description The description as published by the source.

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…

Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details