{"id":"OESA-2026-4913","summary":"git security update","details":"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.\r\n\r\nSecurity Fix(es):\n\nAffected versions of Git have a heap buffer overflow in the three-way merge\ncode (xdiff), which an attacker can trigger through a repository they\ncontrol.\n\nWhen Git merges a file, it first adds up the size of the merged\noutput, allocates a buffer of that size, and then writes the output into\nit. That total was kept in a 32-bit signed integer. The\nconflict-marker-size attribute, which can be set from a committed\n.gitattributes file, accepts any positive integer, and the markers are\nwritten several times for every conflict. A small file with a huge marker\nsize and many separate conflicts can therefore push the total past 4 GiB,\nso the integer wraps to a small value and Git writes attacker-controlled\nmerge output past the end of a buffer that is too small. At minimum this\ncrashes Git, and because the overflow is large and its contents are largely\nattacker-controlled, worse heap corruption is possible.\n\nAny command that does a textual three-way merge can trigger it, such\nas git-merge(1), git-rebase(1), git-cherry-pick(1), and\ngit-merge-tree(1). The latter is most likely a target for Git forges,\nwhich might use git-merge-tree(1) on the server-side to check\nmergeability. When the server reads attributes from trees in the\nrepository (for example through attr.tree or --attr-source), any\nuser who can push branches and request that they be merged (for\nexample by opening a pull or merge request) can trigger the overflow\nwithout anyone else doing anything, and the data they push is small\nbecause the oversized output only appears during the merge.\n\nThe problem has been patched by computing the size as size_t and\nchecking every addition for overflow, so Git stops with an error\ninstead of overflowing.\n\nServers that cannot upgrade right away can add\n\n* conflict-marker-size=7\n\nto each repository&apos;s info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.(CVE-2026-105437)\n\nGit 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&apos;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)\n\nPath traversal in Git allows writing to arbitrary file via cloning and committing to bad repository(CVE-2026-113408)\n\nArbitrary data can be read or written through git-fast-import(1) and git-fast-export(1) features not marked unsafe(CVE-2026-114466)\n\nOut-of-bounds write possible in Git when git-merge(1) used on tag with more than two GPG signatures(CVE-2026-114467)\n\nOut-of-bounds read can crash git-apply(1) when binary patch inflates to very large size(CVE-2026-114469)","modified":"2026-11-19T02:00:08.247183323Z","published":"2026-11-19T01:42:59Z","upstream":["CVE-2026-105437","CVE-2026-111760","CVE-2026-113408","CVE-2026-114466","CVE-2026-114467","CVE-2026-114469"],"database_specific":{"severity":"High"},"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4913"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-111760"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-113408"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114466"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114467"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114469"}],"affected":[{"package":{"name":"git","ecosystem":"openEuler:24.03-LTS-SP3","purl":"pkg:rpm/openEuler/git&distro=openEuler-24.03-LTS-SP3"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.43.0-14.oe2403sp3"}]}],"ecosystem_specific":{"x86_64":["git-2.43.0-14.oe2403sp3.x86_64.rpm","git-core-2.43.0-14.oe2403sp3.x86_64.rpm","git-daemon-2.43.0-14.oe2403sp3.x86_64.rpm","git-debuginfo-2.43.0-14.oe2403sp3.x86_64.rpm","git-debugsource-2.43.0-14.oe2403sp3.x86_64.rpm"],"aarch64":["git-2.43.0-14.oe2403sp3.aarch64.rpm","git-core-2.43.0-14.oe2403sp3.aarch64.rpm","git-daemon-2.43.0-14.oe2403sp3.aarch64.rpm","git-debuginfo-2.43.0-14.oe2403sp3.aarch64.rpm","git-debugsource-2.43.0-14.oe2403sp3.aarch64.rpm"],"noarch":["git-email-2.43.0-14.oe2403sp3.noarch.rpm","git-gui-2.43.0-14.oe2403sp3.noarch.rpm","git-help-2.43.0-14.oe2403sp3.noarch.rpm","git-svn-2.43.0-14.oe2403sp3.noarch.rpm","git-web-2.43.0-14.oe2403sp3.noarch.rpm","gitk-2.43.0-14.oe2403sp3.noarch.rpm","perl-Git-2.43.0-14.oe2403sp3.noarch.rpm","perl-Git-SVN-2.43.0-14.oe2403sp3.noarch.rpm"],"src":["git-2.43.0-14.oe2403sp3.src.rpm"]},"database_specific":{"source":"https://repo.openeuler.org/security/data/osv/OESA-2026-4913.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}]}