{"id":"CVE-2026-105437","aliases":["ALPINE-CVE-2026-105437","AZL-113311","AZL-113555","AZL-113630","AZL-113633","DEBIAN-CVE-2026-105437","DHI-j3aq-eg6h-4chc-kjcz","UBUNTU-CVE-2026-105437","WID-SEC-W-2026-4476"],"summary":"Heap-based Buffer Overflow in Git","published_at":"2026-11-10T18:34:09.369Z","modified_at":"2026-11-18T20:30:06.770213Z","products":[{"slug":"git","name":"Git","category":"gitops-cicd"}],"rating":{"severity":"high","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","attack_path":"internet_unauthenticated","user_interaction":true,"malicious":false,"vendor_ratings":[{"source":"BSI","rating":"mittel"},{"source":"SUSE","rating":"important"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.0039900001138448715,"percentile":0.3484500050544739,"date":"2026-11-18T00:00:00Z"},"priority":9,"details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","affected_stack":[{"ecosystem":"Debian:12","package":"git","purl":"pkg:deb/debian/git?arch=source&distro=bookworm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.39.2+next.20230215-1","1:2.39.2-1.1","1:2.39.5-0+deb12u1","1:2.39.5-0+deb12u2","1:2.39.5-0+deb12u3","1:2.40.0+next.20230313-1","1:2.40.0+next.20230319-1","1:2.40.0-1","1:2.40.0-1+alpha.1","1:2.40.1+next.20230424-1","1:2.40.1+next.20230427-1","1:2.40.1-1","1:2.40.1-1+alpha.1","1:2.42.0-1","1:2.43.0+next.20231120-1","1:2.43.0+next.20240104-1","1:2.43.0-1","1:2.43.0-1+alpha.2","1:2.45.1+next.20240516-1","1:2.45.1-1","1:2.45.2+next.20240614-1","1:2.45.2-1","1:2.45.2-1+alpha.1","1:2.45.2-1.1","1:2.45.2-1.1+alpha.1","1:2.45.2-1.2","1:2.45.2-1.3","1:2.47.1-1","1:2.47.2-0.1","1:2.47.2-0.2","1:2.48.0~rc1+next.20250101-1","1:2.49.0+next.20250314-1","1:2.49.0-1","1:2.49.0-2","1:2.49.0-3","1:2.50.0+next.20250615-1","1:2.50.0-1","1:2.50.0~rc0+next.20250528-1","1:2.50.1-0.1","1:2.51.0+next.20250825-1","1:2.51.0-1","1:2.53.0+next.20260227-1","1:2.53.0-1","1:2.53.0-1+hurd.1","1:2.55.0+next.20260731-1","1:2.55.0-1"],"provider":"osv","source":"DEBIAN-CVE-2026-105437","relation":"self"},{"ecosystem":"Debian:13","package":"git","purl":"pkg:deb/debian/git?arch=source&distro=trixie","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.47.2-0.2","1:2.47.3-0+deb13u1","1:2.48.0~rc1+next.20250101-1","1:2.49.0+next.20250314-1","1:2.49.0-1","1:2.49.0-2","1:2.49.0-3","1:2.50.0+next.20250615-1","1:2.50.0-1","1:2.50.0~rc0+next.20250528-1","1:2.50.1-0.1","1:2.51.0+next.20250825-1","1:2.51.0-1","1:2.53.0+next.20260227-1","1:2.53.0-1","1:2.53.0-1+hurd.1","1:2.55.0+next.20260731-1","1:2.55.0-1"],"provider":"osv","source":"DEBIAN-CVE-2026-105437","relation":"self"},{"ecosystem":"Debian:14","package":"git","purl":"pkg:deb/debian/git?arch=source&distro=forky","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.47.2-0.2","1:2.48.0~rc1+next.20250101-1","1:2.49.0+next.20250314-1","1:2.49.0-1","1:2.49.0-2","1:2.49.0-3","1:2.50.0+next.20250615-1","1:2.50.0-1","1:2.50.0~rc0+next.20250528-1","1:2.50.1-0.1","1:2.51.0+next.20250825-1","1:2.51.0-1","1:2.53.0+next.20260227-1","1:2.53.0-1","1:2.53.0-1+hurd.1","1:2.55.0+next.20260731-1","1:2.55.0-1"],"provider":"osv","source":"DEBIAN-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:22.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=jammy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.32.0-1ubuntu1","1:2.33.1-1ubuntu1","1:2.34.1-1ubuntu1","1:2.34.1-1ubuntu1.1","1:2.34.1-1ubuntu1.2","1:2.34.1-1ubuntu1.4","1:2.34.1-1ubuntu1.5","1:2.34.1-1ubuntu1.6","1:2.34.1-1ubuntu1.8","1:2.34.1-1ubuntu1.9","1:2.34.1-1ubuntu1.10","1:2.34.1-1ubuntu1.11","1:2.34.1-1ubuntu1.12","1:2.34.1-1ubuntu1.13","1:2.34.1-1ubuntu1.14","1:2.34.1-1ubuntu1.15","1:2.34.1-1ubuntu1.16","1:2.34.1-1ubuntu1.17","1:2.34.1-1ubuntu1.18"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:24.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=noble","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.40.1-1ubuntu1","1:2.43.0-1ubuntu1","1:2.43.0-1ubuntu5","1:2.43.0-1ubuntu6","1:2.43.0-1ubuntu7","1:2.43.0-1ubuntu7.1","1:2.43.0-1ubuntu7.2","1:2.43.0-1ubuntu7.3","1:2.43.0-1ubuntu7.4"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:26.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=resolute","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.51.0-1ubuntu1","1:2.53.0-1ubuntu1","1:2.53.0-1ubuntu1.1"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:26.10","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=stonking","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.53.0-1ubuntu1","1:2.55.0-1ubuntu1","1:2.55.0-1ubuntu1.1"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=esm-infra%2Fxenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.5.0-1","1:2.6.2-1","1:2.6.3-1","1:2.6.4-1","1:2.7.0~rc3-1","1:2.7.0-1","1:2.7.3-0ubuntu1","1:2.7.4-0ubuntu1","1:2.7.4-0ubuntu1.1","1:2.7.4-0ubuntu1.2","1:2.7.4-0ubuntu1.3","1:2.7.4-0ubuntu1.4","1:2.7.4-0ubuntu1.5","1:2.7.4-0ubuntu1.6","1:2.7.4-0ubuntu1.7","1:2.7.4-0ubuntu1.8","1:2.7.4-0ubuntu1.9","1:2.7.4-0ubuntu1.10","1:2.7.4-0ubuntu1.10+esm1","1:2.7.4-0ubuntu1.10+esm3","1:2.7.4-0ubuntu1.10+esm4","1:2.7.4-0ubuntu1.10+esm5","1:2.7.4-0ubuntu1.10+esm6","1:2.7.4-0ubuntu1.10+esm7","1:2.7.4-0ubuntu1.10+esm8","1:2.7.4-0ubuntu1.10+esm9","1:2.7.4-0ubuntu1.10+esm10","1:2.7.4-0ubuntu1.10+esm11","1:2.7.4-0ubuntu1.10+esm13"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=esm-infra%2Fbionic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.14.1-1ubuntu4","1:2.15.1-1ubuntu2","1:2.17.0-1ubuntu1","1:2.17.1-1ubuntu0.1","1:2.17.1-1ubuntu0.3","1:2.17.1-1ubuntu0.4","1:2.17.1-1ubuntu0.5","1:2.17.1-1ubuntu0.6","1:2.17.1-1ubuntu0.7","1:2.17.1-1ubuntu0.8","1:2.17.1-1ubuntu0.9","1:2.17.1-1ubuntu0.10","1:2.17.1-1ubuntu0.11","1:2.17.1-1ubuntu0.12","1:2.17.1-1ubuntu0.13","1:2.17.1-1ubuntu0.14","1:2.17.1-1ubuntu0.15","1:2.17.1-1ubuntu0.16","1:2.17.1-1ubuntu0.17","1:2.17.1-1ubuntu0.18","1:2.17.1-1ubuntu0.18+esm1","1:2.17.1-1ubuntu0.18+esm2","1:2.17.1-1ubuntu0.18+esm3","1:2.17.1-1ubuntu0.18+esm4","1:2.17.1-1ubuntu0.18+esm6","1:2.17.1-1ubuntu0.18+esm8"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=esm-infra%2Ffocal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.20.1-2ubuntu1","1:2.24.0-1ubuntu1","1:2.24.0-1ubuntu2","1:2.25.0-1ubuntu1","1:2.25.1-1ubuntu1","1:2.25.1-1ubuntu2","1:2.25.1-1ubuntu3","1:2.25.1-1ubuntu3.1","1:2.25.1-1ubuntu3.2","1:2.25.1-1ubuntu3.3","1:2.25.1-1ubuntu3.4","1:2.25.1-1ubuntu3.5","1:2.25.1-1ubuntu3.6","1:2.25.1-1ubuntu3.7","1:2.25.1-1ubuntu3.8","1:2.25.1-1ubuntu3.10","1:2.25.1-1ubuntu3.11","1:2.25.1-1ubuntu3.12","1:2.25.1-1ubuntu3.13","1:2.25.1-1ubuntu3.14","1:2.25.1-1ubuntu3.14+esm1","1:2.25.1-1ubuntu3.14+esm2","1:2.25.1-1ubuntu3.14+esm3","1:2.25.1-1ubuntu3.14+esm4","1:2.25.1-1ubuntu3.14+esm5","1:2.25.1-1ubuntu3.14+esm6"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"}],"affected_other":[{"ecosystem":"Alpine:v3.23","package":"git","purl":"pkg:apk/alpine/git?arch=source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.52.1-r0"}]}],"fixed":["2.52.1-r0"],"provider":"osv","source":"ALPINE-CVE-2026-105437","relation":"self"},{"ecosystem":"Alpine:v3.24","package":"git","purl":"pkg:apk/alpine/git?arch=source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.54.1-r0"}]}],"fixed":["2.54.1-r0"],"provider":"osv","source":"ALPINE-CVE-2026-105437","relation":"self"},{"ecosystem":"Azure Linux:3","package":"git","purl":"pkg:rpm/azure-linux/git","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.45.4-3"}]}],"provider":"osv","source":"AZL-113311","relation":"self"},{"ecosystem":"Azure Linux:3","package":"libgit2","purl":"pkg:rpm/azure-linux/libgit2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.7.2-3"}]}],"provider":"osv","source":"AZL-113555","relation":"self"},{"ecosystem":"Azure Linux:3","package":"rust","purl":"pkg:rpm/azure-linux/rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.75.0-31"}]}],"provider":"osv","source":"AZL-113630","relation":"self"},{"ecosystem":"Azure Linux:3","package":"rust","purl":"pkg:rpm/azure-linux/rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.85.0"},{"last_affected":"1.98.1-1"}]}],"provider":"osv","source":"AZL-113633","relation":"self"},{"ecosystem":"CVE","package":"Git/Git","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.49.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.50.0-rc0"},{"fixed":"2.50.2"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.51.0-rc0"},{"fixed":"2.51.3"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.52.0-rc0"},{"fixed":"2.52.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.53.0-rc0"},{"fixed":"2.53.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.54.0-rc0"},{"fixed":"2.54.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.55.0-rc0"},{"fixed":"2.55.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.56.0-rc0"},{"fixed":"2.56.1"}]}],"fixed":["2.49.1","2.50.2","2.51.3","2.52.1","2.53.1","2.54.1","2.55.1","2.56.1"],"provider":"cvelistv5","source":"CVE-2026-105437","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"git","purl":"pkg:apk/dhi/git","versions":["2.52.0-r0","2.52.1-r0","2.54.0-r0","2.55.0-r0","2.55.0-r1","2.56.0-r0","2.56.1-r0"],"provider":"osv","source":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"git","purl":"pkg:apk/dhi/git","versions":["2.54.0-r0","2.54.1-r0","2.55.0-r0","2.55.0-r1"],"provider":"osv","source":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self"},{"ecosystem":"Docker Hardened Images:Debian:13","package":"git","purl":"pkg:deb/dhi/git","versions":["1:2.47.3-0+deb13u1+dhi0","1:2.47.3-0+deb13u1+dhi1","1:2.47.3-0+deb13u1+dhi2","1:2.47.3-0+deb13u1+dhi3"],"provider":"osv","source":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self"},{"ecosystem":"openSUSE:Tumbleweed","package":"git","purl":"pkg:rpm/opensuse/git&distro=openSUSE%20Tumbleweed","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.56.1-1.1"}]}],"fixed":["2.56.1-1.1"],"provider":"osv","source":"openSUSE-SU-2026:12538-1","relation":"upstream"}],"product_status":[{"vendor":"BSI","product":"Amazon Linux 2","cpe":"cpe:/o:amazon:linux_2:-","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Gentoo Linux","cpe":"cpe:/o:gentoo:linux:-","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Open Source GitLab <19.3.8","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Open Source GitLab <19.4.6","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Open Source GitLab <19.5.4","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"SUSE","product":"openSUSE Tumbleweed","cpe":"cpe:/o:opensuse:tumbleweed","status":"fixed","packages":["git","git-arch","git-core","git-credential-libsecret","git-cvs","git-daemon","git-doc","git-email","git-gui","git-p4","git-svn","git-web","gitk","perl-Git"],"package_count":14,"fixed":["git-2.56.1-1.1","git-arch-2.56.1-1.1","git-core-2.56.1-1.1","git-credential-libsecret-2.56.1-1.1","git-cvs-2.56.1-1.1","git-daemon-2.56.1-1.1","git-doc-2.56.1-1.1","git-email-2.56.1-1.1","git-gui-2.56.1-1.1","git-p4-2.56.1-1.1","git-svn-2.56.1-1.1","git-web-2.56.1-1.1","gitk-2.56.1-1.1","perl-Git-2.56.1-1.1"],"advisories":[],"provider":"csaf-suse","source":"CVE-2026-105437"}],"records":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4455","relation":"upstream","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4455","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-11-10T23:00:00Z","modified_at":"2026-11-17T23:00:00Z","summary":"git: Mehrere Schwachstellen","details":"Ein Angreifer kann mehrere Schwachstellen in git ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen und um Dateien zu manipulieren.\n\nGit ist eine freie Software zur verteilten Versionsverwaltung von Dateien.","severity":[{"type":"BSI","score":"hoch","source":"WID-SEC-W-2026-4455"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4455.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4455"},{"type":"WEB","url":"https://github.blog/open-source/git/git-security-vulnerabilities-announced-7/"},{"type":"WEB","url":"https://alas.aws.amazon.com/AL2/ALAS2-2026-4109.html"},{"type":"WEB","url":"https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.5"}]},{"provider":"csaf-suse","source_id":"openSUSE-SU-2026:12538-1","relation":"upstream","url":"https://www.suse.com/security/cve/CVE-2026-105437/","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-11-13T00:00:00Z","modified_at":"2026-11-13T00:00:00Z","summary":"git-2.56.1-1.1 on GA media","details":"git-2.56.1-1.1 on GA media\n\nThese are all security issues fixed in the git-2.56.1-1.1 package on the GA media of openSUSE Tumbleweed.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","source":"openSUSE-SU-2026:12538-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","source":"openSUSE-SU-2026:12538-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"openSUSE-SU-2026:12538-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"openSUSE-SU-2026:12538-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","source":"openSUSE-SU-2026:12538-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","source":"openSUSE-SU-2026:12538-1"},{"type":"SUSE","score":"moderate","source":"openSUSE-SU-2026:12538-1"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://www.suse.com/support/security/rating/"},{"type":"WEB","url":"https://ftp.suse.com/pub/projects/security/csaf/2026/opensuse-su-2026_12538-1.json"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105437/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111760/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113408/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114466/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114467/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114469/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105437"},{"type":"WEB","url":"https://bugzilla.suse.com/1289505"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111760"},{"type":"WEB","url":"https://bugzilla.suse.com/1289501"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113408"},{"type":"WEB","url":"https://bugzilla.suse.com/1289502"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114466"},{"type":"WEB","url":"https://bugzilla.suse.com/1289506"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114467"},{"type":"WEB","url":"https://bugzilla.suse.com/1289503"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114469"},{"type":"WEB","url":"https://bugzilla.suse.com/1289504"}]},{"provider":"osv","source_id":"openSUSE-SU-2026:12538-1","relation":"upstream","url":"https://osv.dev/vulnerability/openSUSE-SU-2026:12538-1","published_at":"2026-11-13T00:00:00Z","modified_at":"2026-11-14T17:23:11.347328Z","summary":"git-2.56.1-1.1 on GA media","details":"These are all security issues fixed in the git-2.56.1-1.1 package on the GA media of openSUSE Tumbleweed.","severity":[],"affected":[{"ecosystem":"openSUSE:Tumbleweed","package":"git","purl":"pkg:rpm/opensuse/git&distro=openSUSE%20Tumbleweed","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.56.1-1.1"}]}],"fixed":["2.56.1-1.1"],"provider":"osv","source":"openSUSE-SU-2026:12538-1","relation":"upstream"}],"product_status":[],"references":[{"type":"ADVISORY","url":""},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105437"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111760"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113408"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114466"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114467"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-114469"}]},{"provider":"cvelistv5","source_id":"CVE-2026-105437","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-105437","license":"CC-BY-4.0","published_at":"2026-11-10T18:34:09.369Z","modified_at":"2026-11-16T18:22:21.207Z","summary":"Heap-based Buffer Overflow in Git","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"CVE-2026-105437"}],"affected":[{"ecosystem":"CVE","package":"Git/Git","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.49.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.50.0-rc0"},{"fixed":"2.50.2"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.51.0-rc0"},{"fixed":"2.51.3"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.52.0-rc0"},{"fixed":"2.52.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.53.0-rc0"},{"fixed":"2.53.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.54.0-rc0"},{"fixed":"2.54.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.55.0-rc0"},{"fixed":"2.55.1"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.56.0-rc0"},{"fixed":"2.56.1"}]}],"fixed":["2.49.1","2.50.2","2.51.3","2.52.1","2.53.1","2.54.1","2.55.1","2.56.1"],"provider":"cvelistv5","source":"CVE-2026-105437","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://gitlab.com/gitlab-org/git/-/work_items/814"},{"type":"WEB","url":"https://gitlab.com/gitlab-org/gitlab/-/work_items/632121"},{"type":"EXPLOIT","url":"https://hackerone.com/reports/4044249"}]},{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4476","relation":"self","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4476","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-11-10T23:00:00Z","modified_at":"2026-11-12T23:00:00Z","summary":"GitLab: Schwachstelle ermöglicht Codeausführung","details":"Ein entfernter, anonymer Angreifer kann eine Schwachstelle in GitLab ausnutzen, um beliebigen Programmcode auszuführen.\n\nGitLab ist eine Webanwendung zur Versionsverwaltung für Softwareprojekte auf Basis von git.","severity":[{"type":"BSI","score":"mittel","source":"WID-SEC-W-2026-4476"}],"affected":[],"product_status":[{"vendor":"BSI","product":"Amazon Linux 2","cpe":"cpe:/o:amazon:linux_2:-","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Gentoo Linux","cpe":"cpe:/o:gentoo:linux:-","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Open Source GitLab <19.3.8","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Open Source GitLab <19.4.6","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"},{"vendor":"BSI","product":"Open Source GitLab <19.5.4","status":"affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"provider":"csaf-bsi","source":"WID-SEC-W-2026-4476"}],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4476.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4476"},{"type":"WEB","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-105437"},{"type":"WEB","url":"https://security.gentoo.org/glsa/202611-02"},{"type":"WEB","url":"https://alas.aws.amazon.com/AL2/ALAS2-2026-4109.html"}]},{"provider":"csaf-suse","source_id":"CVE-2026-105437","relation":"self","url":"https://www.suse.com/security/cve/CVE-2026-105437/","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-11-11T17:40:18Z","modified_at":"2026-11-14T00:47:09Z","summary":"SUSE CVE CVE-2026-105437","details":"SUSE CVE-2026-105437\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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"CVE-2026-105437"},{"type":"SUSE","score":"important","source":"CVE-2026-105437"}],"affected":[],"product_status":[{"vendor":"SUSE","product":"openSUSE Tumbleweed","cpe":"cpe:/o:opensuse:tumbleweed","status":"fixed","packages":["git","git-arch","git-core","git-credential-libsecret","git-cvs","git-daemon","git-doc","git-email","git-gui","git-p4","git-svn","git-web","gitk","perl-Git"],"package_count":14,"fixed":["git-2.56.1-1.1","git-arch-2.56.1-1.1","git-core-2.56.1-1.1","git-credential-libsecret-2.56.1-1.1","git-cvs-2.56.1-1.1","git-daemon-2.56.1-1.1","git-doc-2.56.1-1.1","git-email-2.56.1-1.1","git-gui-2.56.1-1.1","git-p4-2.56.1-1.1","git-svn-2.56.1-1.1","git-web-2.56.1-1.1","gitk-2.56.1-1.1","perl-Git-2.56.1-1.1"],"advisories":[],"provider":"csaf-suse","source":"CVE-2026-105437"}],"references":[{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105437"},{"type":"WEB","url":"https://www.suse.com/support/security/rating/"},{"type":"WEB","url":"https://bugzilla.suse.com/1289505"}]},{"provider":"osv","source_id":"ALPINE-CVE-2026-105437","relation":"self","url":"https://osv.dev/vulnerability/ALPINE-CVE-2026-105437","published_at":"2026-11-10T19:17:46.2Z","modified_at":"2026-11-11T09:30:02.975374Z","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"ALPINE-CVE-2026-105437"}],"affected":[{"ecosystem":"Alpine:v3.23","package":"git","purl":"pkg:apk/alpine/git?arch=source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.52.1-r0"}]}],"fixed":["2.52.1-r0"],"provider":"osv","source":"ALPINE-CVE-2026-105437","relation":"self"},{"ecosystem":"Alpine:v3.24","package":"git","purl":"pkg:apk/alpine/git?arch=source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.54.1-r0"}]}],"fixed":["2.54.1-r0"],"provider":"osv","source":"ALPINE-CVE-2026-105437","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://security.alpinelinux.org/vuln/CVE-2026-105437"}]},{"provider":"osv","source_id":"AZL-113311","relation":"self","url":"https://osv.dev/vulnerability/AZL-113311","license":"MIT","published_at":"2026-11-10T19:17:46Z","modified_at":"2026-11-18T05:33:41Z","summary":"CVE-2026-105437 affecting package git 2.45.4-3","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[],"affected":[{"ecosystem":"Azure Linux:3","package":"git","purl":"pkg:rpm/azure-linux/git","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.45.4-3"}]}],"provider":"osv","source":"AZL-113311","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"}]},{"provider":"osv","source_id":"AZL-113555","relation":"self","url":"https://osv.dev/vulnerability/AZL-113555","license":"MIT","published_at":"2026-11-10T19:17:46Z","modified_at":"2026-11-18T05:33:41Z","summary":"CVE-2026-105437 affecting package libgit2 1.7.2-3","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[],"affected":[{"ecosystem":"Azure Linux:3","package":"libgit2","purl":"pkg:rpm/azure-linux/libgit2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.7.2-3"}]}],"provider":"osv","source":"AZL-113555","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"}]},{"provider":"osv","source_id":"AZL-113630","relation":"self","url":"https://osv.dev/vulnerability/AZL-113630","license":"MIT","published_at":"2026-11-10T19:17:46Z","modified_at":"2026-11-16T05:30:07Z","summary":"CVE-2026-105437 affecting package rust 1.75.0-31","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[],"affected":[{"ecosystem":"Azure Linux:3","package":"rust","purl":"pkg:rpm/azure-linux/rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.75.0-31"}]}],"provider":"osv","source":"AZL-113630","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"}]},{"provider":"osv","source_id":"AZL-113633","relation":"self","url":"https://osv.dev/vulnerability/AZL-113633","license":"MIT","published_at":"2026-11-10T19:17:46Z","modified_at":"2026-11-16T05:30:07Z","summary":"CVE-2026-105437 affecting package rust 1.98.1-1","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[],"affected":[{"ecosystem":"Azure Linux:3","package":"rust","purl":"pkg:rpm/azure-linux/rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.85.0"},{"last_affected":"1.98.1-1"}]}],"provider":"osv","source":"AZL-113633","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"}]},{"provider":"osv","source_id":"DEBIAN-CVE-2026-105437","relation":"self","url":"https://osv.dev/vulnerability/DEBIAN-CVE-2026-105437","published_at":"2026-11-10T19:17:46.2Z","modified_at":"2026-11-17T09:47:28.641579Z","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"DEBIAN-CVE-2026-105437"}],"affected":[{"ecosystem":"Debian:12","package":"git","purl":"pkg:deb/debian/git?arch=source&distro=bookworm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.39.2+next.20230215-1","1:2.39.2-1.1","1:2.39.5-0+deb12u1","1:2.39.5-0+deb12u2","1:2.39.5-0+deb12u3","1:2.40.0+next.20230313-1","1:2.40.0+next.20230319-1","1:2.40.0-1","1:2.40.0-1+alpha.1","1:2.40.1+next.20230424-1","1:2.40.1+next.20230427-1","1:2.40.1-1","1:2.40.1-1+alpha.1","1:2.42.0-1","1:2.43.0+next.20231120-1","1:2.43.0+next.20240104-1","1:2.43.0-1","1:2.43.0-1+alpha.2","1:2.45.1+next.20240516-1","1:2.45.1-1","1:2.45.2+next.20240614-1","1:2.45.2-1","1:2.45.2-1+alpha.1","1:2.45.2-1.1","1:2.45.2-1.1+alpha.1","1:2.45.2-1.2","1:2.45.2-1.3","1:2.47.1-1","1:2.47.2-0.1","1:2.47.2-0.2","1:2.48.0~rc1+next.20250101-1","1:2.49.0+next.20250314-1","1:2.49.0-1","1:2.49.0-2","1:2.49.0-3","1:2.50.0+next.20250615-1","1:2.50.0-1","1:2.50.0~rc0+next.20250528-1","1:2.50.1-0.1","1:2.51.0+next.20250825-1","1:2.51.0-1","1:2.53.0+next.20260227-1","1:2.53.0-1","1:2.53.0-1+hurd.1","1:2.55.0+next.20260731-1","1:2.55.0-1"],"provider":"osv","source":"DEBIAN-CVE-2026-105437","relation":"self"},{"ecosystem":"Debian:13","package":"git","purl":"pkg:deb/debian/git?arch=source&distro=trixie","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.47.2-0.2","1:2.47.3-0+deb13u1","1:2.48.0~rc1+next.20250101-1","1:2.49.0+next.20250314-1","1:2.49.0-1","1:2.49.0-2","1:2.49.0-3","1:2.50.0+next.20250615-1","1:2.50.0-1","1:2.50.0~rc0+next.20250528-1","1:2.50.1-0.1","1:2.51.0+next.20250825-1","1:2.51.0-1","1:2.53.0+next.20260227-1","1:2.53.0-1","1:2.53.0-1+hurd.1","1:2.55.0+next.20260731-1","1:2.55.0-1"],"provider":"osv","source":"DEBIAN-CVE-2026-105437","relation":"self"},{"ecosystem":"Debian:14","package":"git","purl":"pkg:deb/debian/git?arch=source&distro=forky","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.47.2-0.2","1:2.48.0~rc1+next.20250101-1","1:2.49.0+next.20250314-1","1:2.49.0-1","1:2.49.0-2","1:2.49.0-3","1:2.50.0+next.20250615-1","1:2.50.0-1","1:2.50.0~rc0+next.20250528-1","1:2.50.1-0.1","1:2.51.0+next.20250825-1","1:2.51.0-1","1:2.53.0+next.20260227-1","1:2.53.0-1","1:2.53.0-1+hurd.1","1:2.55.0+next.20260731-1","1:2.55.0-1"],"provider":"osv","source":"DEBIAN-CVE-2026-105437","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2026-105437"}]},{"provider":"osv","source_id":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self","url":"https://osv.dev/vulnerability/DHI-j3aq-eg6h-4chc-kjcz","license":"Apache-2.0","published_at":"2026-11-11T18:18:24Z","modified_at":"2026-11-18T20:30:06.770213Z","summary":"Affected versions of Git have a heap buffer overflow in the three-way merge","details":"Affected 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's info/attributes as a workaround, which overrides\nany in-tree .gitattributes, or turn off server-side mergeability checks for\nuntrusted repositories.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"DHI-j3aq-eg6h-4chc-kjcz"}],"affected":[{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"git","purl":"pkg:apk/dhi/git","versions":["2.52.0-r0","2.52.1-r0","2.54.0-r0","2.55.0-r0","2.55.0-r1","2.56.0-r0","2.56.1-r0"],"provider":"osv","source":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"git","purl":"pkg:apk/dhi/git","versions":["2.54.0-r0","2.54.1-r0","2.55.0-r0","2.55.0-r1"],"provider":"osv","source":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self"},{"ecosystem":"Docker Hardened Images:Debian:13","package":"git","purl":"pkg:deb/dhi/git","versions":["1:2.47.3-0+deb13u1+dhi0","1:2.47.3-0+deb13u1+dhi1","1:2.47.3-0+deb13u1+dhi2","1:2.47.3-0+deb13u1+dhi3"],"provider":"osv","source":"DHI-j3aq-eg6h-4chc-kjcz","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://scout.docker.com/v/DHI-j3aq-eg6h-4chc-kjcz"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"},{"type":"ADVISORY","url":"https://security.alpinelinux.org/vuln/CVE-2026-105437"},{"type":"ADVISORY","url":"https://alas.aws.amazon.com/AL2/ALAS-2026-4109.html"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114469"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114467"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114466"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-113408"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-111760"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-105437"},{"type":"ADVISORY","url":"https://alas.aws.amazon.com/AL2023/ALAS-2026-3445.html"},{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2026-105437"},{"type":"ADVISORY","url":"https://access.redhat.com/security/cve/CVE-2026-105437"},{"type":"ADVISORY","url":"https://ubuntu.com/security/CVE-2026-105437"},{"type":"ADVISORY","url":"http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-105437"}]},{"provider":"osv","source_id":"UBUNTU-CVE-2026-105437","relation":"self","url":"https://osv.dev/vulnerability/UBUNTU-CVE-2026-105437","license":"CC-BY-SA-4.0","published_at":"2026-11-10T19:17:00Z","modified_at":"2026-11-18T11:14:32Z","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","source":"UBUNTU-CVE-2026-105437"},{"type":"Ubuntu","score":"medium","source":"UBUNTU-CVE-2026-105437"}],"affected":[{"ecosystem":"Ubuntu:22.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=jammy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.32.0-1ubuntu1","1:2.33.1-1ubuntu1","1:2.34.1-1ubuntu1","1:2.34.1-1ubuntu1.1","1:2.34.1-1ubuntu1.2","1:2.34.1-1ubuntu1.4","1:2.34.1-1ubuntu1.5","1:2.34.1-1ubuntu1.6","1:2.34.1-1ubuntu1.8","1:2.34.1-1ubuntu1.9","1:2.34.1-1ubuntu1.10","1:2.34.1-1ubuntu1.11","1:2.34.1-1ubuntu1.12","1:2.34.1-1ubuntu1.13","1:2.34.1-1ubuntu1.14","1:2.34.1-1ubuntu1.15","1:2.34.1-1ubuntu1.16","1:2.34.1-1ubuntu1.17","1:2.34.1-1ubuntu1.18"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:24.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=noble","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.40.1-1ubuntu1","1:2.43.0-1ubuntu1","1:2.43.0-1ubuntu5","1:2.43.0-1ubuntu6","1:2.43.0-1ubuntu7","1:2.43.0-1ubuntu7.1","1:2.43.0-1ubuntu7.2","1:2.43.0-1ubuntu7.3","1:2.43.0-1ubuntu7.4"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:26.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=resolute","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.51.0-1ubuntu1","1:2.53.0-1ubuntu1","1:2.53.0-1ubuntu1.1"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:26.10","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=stonking","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.53.0-1ubuntu1","1:2.55.0-1ubuntu1","1:2.55.0-1ubuntu1.1"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=esm-infra%2Fxenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.5.0-1","1:2.6.2-1","1:2.6.3-1","1:2.6.4-1","1:2.7.0~rc3-1","1:2.7.0-1","1:2.7.3-0ubuntu1","1:2.7.4-0ubuntu1","1:2.7.4-0ubuntu1.1","1:2.7.4-0ubuntu1.2","1:2.7.4-0ubuntu1.3","1:2.7.4-0ubuntu1.4","1:2.7.4-0ubuntu1.5","1:2.7.4-0ubuntu1.6","1:2.7.4-0ubuntu1.7","1:2.7.4-0ubuntu1.8","1:2.7.4-0ubuntu1.9","1:2.7.4-0ubuntu1.10","1:2.7.4-0ubuntu1.10+esm1","1:2.7.4-0ubuntu1.10+esm3","1:2.7.4-0ubuntu1.10+esm4","1:2.7.4-0ubuntu1.10+esm5","1:2.7.4-0ubuntu1.10+esm6","1:2.7.4-0ubuntu1.10+esm7","1:2.7.4-0ubuntu1.10+esm8","1:2.7.4-0ubuntu1.10+esm9","1:2.7.4-0ubuntu1.10+esm10","1:2.7.4-0ubuntu1.10+esm11","1:2.7.4-0ubuntu1.10+esm13"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=esm-infra%2Fbionic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.14.1-1ubuntu4","1:2.15.1-1ubuntu2","1:2.17.0-1ubuntu1","1:2.17.1-1ubuntu0.1","1:2.17.1-1ubuntu0.3","1:2.17.1-1ubuntu0.4","1:2.17.1-1ubuntu0.5","1:2.17.1-1ubuntu0.6","1:2.17.1-1ubuntu0.7","1:2.17.1-1ubuntu0.8","1:2.17.1-1ubuntu0.9","1:2.17.1-1ubuntu0.10","1:2.17.1-1ubuntu0.11","1:2.17.1-1ubuntu0.12","1:2.17.1-1ubuntu0.13","1:2.17.1-1ubuntu0.14","1:2.17.1-1ubuntu0.15","1:2.17.1-1ubuntu0.16","1:2.17.1-1ubuntu0.17","1:2.17.1-1ubuntu0.18","1:2.17.1-1ubuntu0.18+esm1","1:2.17.1-1ubuntu0.18+esm2","1:2.17.1-1ubuntu0.18+esm3","1:2.17.1-1ubuntu0.18+esm4","1:2.17.1-1ubuntu0.18+esm6","1:2.17.1-1ubuntu0.18+esm8"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"git","purl":"pkg:deb/ubuntu/git?arch=source&distro=esm-infra%2Ffocal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.20.1-2ubuntu1","1:2.24.0-1ubuntu1","1:2.24.0-1ubuntu2","1:2.25.0-1ubuntu1","1:2.25.1-1ubuntu1","1:2.25.1-1ubuntu2","1:2.25.1-1ubuntu3","1:2.25.1-1ubuntu3.1","1:2.25.1-1ubuntu3.2","1:2.25.1-1ubuntu3.3","1:2.25.1-1ubuntu3.4","1:2.25.1-1ubuntu3.5","1:2.25.1-1ubuntu3.6","1:2.25.1-1ubuntu3.7","1:2.25.1-1ubuntu3.8","1:2.25.1-1ubuntu3.10","1:2.25.1-1ubuntu3.11","1:2.25.1-1ubuntu3.12","1:2.25.1-1ubuntu3.13","1:2.25.1-1ubuntu3.14","1:2.25.1-1ubuntu3.14+esm1","1:2.25.1-1ubuntu3.14+esm2","1:2.25.1-1ubuntu3.14+esm3","1:2.25.1-1ubuntu3.14+esm4","1:2.25.1-1ubuntu3.14+esm5","1:2.25.1-1ubuntu3.14+esm6"],"provider":"osv","source":"UBUNTU-CVE-2026-105437","relation":"self"}],"product_status":[],"references":[{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-105437"},{"type":"REPORT","url":"https://www.cve.org/CVERecord?id=CVE-2026-105437"},{"type":"REPORT","url":"https://lore.kernel.org/git/xmqqh5hosgw5.fsf@gitster.g/"},{"type":"REPORT","url":"https://github.blog/open-source/git/git-security-vulnerabilities-announced-7/"},{"type":"REPORT","url":"https://gitlab.com/gitlab-org/git/-/work_items/814"},{"type":"REPORT","url":"https://gitlab.com/gitlab-org/gitlab/-/work_items/632121"},{"type":"REPORT","url":"https://hackerone.com/reports/4044249"}]}],"references":[{"type":"WEB","url":"https://gitlab.com/gitlab-org/git/-/work_items/814"},{"type":"WEB","url":"https://gitlab.com/gitlab-org/gitlab/-/work_items/632121"},{"type":"EXPLOIT","url":"https://hackerone.com/reports/4044249"},{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4476.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4476"},{"type":"WEB","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-105437"},{"type":"WEB","url":"https://security.gentoo.org/glsa/202611-02"},{"type":"WEB","url":"https://alas.aws.amazon.com/AL2/ALAS2-2026-4109.html"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105437"},{"type":"WEB","url":"https://www.suse.com/support/security/rating/"},{"type":"WEB","url":"https://bugzilla.suse.com/1289505"},{"type":"ADVISORY","url":"https://security.alpinelinux.org/vuln/CVE-2026-105437"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"},{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2026-105437"},{"type":"ADVISORY","url":"https://scout.docker.com/v/DHI-j3aq-eg6h-4chc-kjcz"},{"type":"ADVISORY","url":"https://alas.aws.amazon.com/AL2/ALAS-2026-4109.html"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114469"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114467"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114466"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-113408"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-111760"},{"type":"ADVISORY","url":"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-105437"},{"type":"ADVISORY","url":"https://alas.aws.amazon.com/AL2023/ALAS-2026-3445.html"},{"type":"ADVISORY","url":"https://access.redhat.com/security/cve/CVE-2026-105437"},{"type":"ADVISORY","url":"https://ubuntu.com/security/CVE-2026-105437"},{"type":"ADVISORY","url":"http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-105437"},{"type":"REPORT","url":"https://lore.kernel.org/git/xmqqh5hosgw5.fsf@gitster.g/"},{"type":"REPORT","url":"https://github.blog/open-source/git/git-security-vulnerabilities-announced-7/"}],"sources":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4455","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4455","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-17T23:00:00Z","relation":"upstream"},{"provider":"csaf-suse","source_id":"openSUSE-SU-2026:12538-1","url":"https://www.suse.com/security/cve/CVE-2026-105437/","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-13T00:00:00Z","relation":"upstream"},{"provider":"osv","source_id":"openSUSE-SU-2026:12538-1","url":"https://osv.dev/vulnerability/openSUSE-SU-2026:12538-1","modified_at":"2026-11-14T17:23:11.347328Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2026-105437","url":"https://www.cve.org/CVERecord?id=CVE-2026-105437","license":"CC-BY-4.0","modified_at":"2026-11-16T18:22:21.207Z","relation":"self"},{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4476","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4476","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-12T23:00:00Z","relation":"self"},{"provider":"csaf-suse","source_id":"CVE-2026-105437","url":"https://www.suse.com/security/cve/CVE-2026-105437/","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-14T00:47:09Z","relation":"self"},{"provider":"osv","source_id":"ALPINE-CVE-2026-105437","url":"https://osv.dev/vulnerability/ALPINE-CVE-2026-105437","modified_at":"2026-11-11T09:30:02.975374Z","relation":"self"},{"provider":"osv","source_id":"AZL-113311","url":"https://osv.dev/vulnerability/AZL-113311","license":"MIT","modified_at":"2026-11-18T05:33:41Z","relation":"self"},{"provider":"osv","source_id":"AZL-113555","url":"https://osv.dev/vulnerability/AZL-113555","license":"MIT","modified_at":"2026-11-18T05:33:41Z","relation":"self"},{"provider":"osv","source_id":"AZL-113630","url":"https://osv.dev/vulnerability/AZL-113630","license":"MIT","modified_at":"2026-11-16T05:30:07Z","relation":"self"},{"provider":"osv","source_id":"AZL-113633","url":"https://osv.dev/vulnerability/AZL-113633","license":"MIT","modified_at":"2026-11-16T05:30:07Z","relation":"self"},{"provider":"osv","source_id":"DEBIAN-CVE-2026-105437","url":"https://osv.dev/vulnerability/DEBIAN-CVE-2026-105437","modified_at":"2026-11-17T09:47:28.641579Z","relation":"self"},{"provider":"osv","source_id":"DHI-j3aq-eg6h-4chc-kjcz","url":"https://osv.dev/vulnerability/DHI-j3aq-eg6h-4chc-kjcz","license":"Apache-2.0","modified_at":"2026-11-18T20:30:06.770213Z","relation":"self"},{"provider":"osv","source_id":"UBUNTU-CVE-2026-105437","url":"https://osv.dev/vulnerability/UBUNTU-CVE-2026-105437","license":"CC-BY-SA-4.0","modified_at":"2026-11-18T11:14:32Z","relation":"self"}]}
