OESA-2026-4914: git security update

Published Nov 19, 2026
·
Updated

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows. Security Fix(es):

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 sizet 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.(CVE-2026-105437)

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Prior to 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1, an attacker-controlled repository hosted by the attacker rather than on a normal forge site can exploit git clone --recurse-submodules by causing Git to overwrite a submodule gitfile with a symbolic link. The symbolic link can point to a directory containing attacker-controlled Git configuration or hooks, allowing those hooks or configuration to execute code on the cloning user's system. The issue requires the recursive-submodule option, and users should avoid cloning repositories from untrusted sources. This issue is fixed in versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1.(CVE-2026-111760)

Path traversal in Git allows writing to arbitrary file via cloning and committing to bad repository(CVE-2026-113408)

Arbitrary data can be read or written through git-fast-import(1) and git-fast-export(1) features not marked unsafe(CVE-2026-114466)

Out-of-bounds write possible in Git when git-merge(1) used on tag with more than two GPG signatures(CVE-2026-114467)

Out-of-bounds read can crash git-apply(1) when binary patch inflates to very large size(CVE-2026-114469)

Affected Software

1 affected componentFixes available
openeuler/git<2.54.1-1.oe2403sp4
2.54.1-1.oe2403sp4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/git to a version that resolves this vulnerability.

    Fixed in 2.54.1-1.oe2403sp4
  2. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.50.2
  3. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.51.3
  4. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.52.1
  5. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.53.1
  6. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.54.1
  7. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.55.1
  8. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.56.1
  9. Configuration

    Add `* conflict-marker-size=7` to each repository's info/attributes to override in-tree .gitattributes.

    Git repository conflict-marker-size = 7
  10. Compensating control

    Turn off server-side mergeability checks for untrusted repositories.

  11. Compensating control

    Avoid cloning repositories from untrusted sources with the recursive-submodule option.

Event History

Nov 19, 2026
Advisory Published
via OSV·01:43 AM
Data Sourced
via OSV·01:43 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Who is exposed to this issue?

Users who merge content from a repository controlled by an attacker are exposed. The trigger occurs during Git's three-way merge processing of a file.

2

What does an attacker need to include in a repository to trigger the overflow?

The repository can contain a committed .gitattributes file that sets an extremely large positive conflict-marker-size value, along with a small file engineered to produce many separate merge conflicts. Repeated conflict-marker output can make Git's 32-bit signed output-size calculation wrap past 4 GiB.

3

Does exploitation require changing local Git configuration?

The described malicious conflict-marker-size attribute can be set in a committed .gitattributes file in the attacker-controlled repository. No local configuration change is described as necessary.

4

What happens when the vulnerable merge is processed?

Git allocates a buffer based on the wrapped, undersized output total and then writes attacker-controlled merge output past the end of that buffer. The advisory rates confidentiality, integrity, and availability impact as high.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203