{"id":"EM-20261110-LYVO","url":"https://cyber.eventmonitor.net/incident/EM-20261110-LYVO/git-vulnerability-cve-2026-105437/","type":"cve","title":"git Vulnerability (CVE-2026-105437)","subtitle":"CVE-2026-105437","subject":"CVE-2026-105437","status":"Developing","severity":"high","affected":[],"headline":null,"born":"2026-11-10T19:17:46.200Z","firstSignal":"2026-11-10T18:00:00.000Z","lastSignal":"2026-11-11T05:53:49.000Z","updated":"2026-11-11T15:44:07.320Z","revision":2,"life":[{"status":"Born","at":"2026-11-10T19:17:46.200Z","why":"second independent source: C6 NVD CVE API 2.0"},{"status":"Developing","at":"2026-11-10T19:17:46.200Z","why":"signals keep joining"}],"changeLog":[{"at":"2026-11-10T18:00:00.000Z","what":"First signal: C41 Red Hat Security Data"},{"at":"2026-11-10T19:17:46.200Z","what":"Born: second source, C6 NVD CVE API 2.0. Page EM-20261110-LYVO created."},{"at":"2026-11-11T05:53:49.000Z","what":"Source joined: C31 Vulners (new public exploits)"}],"stages":[{"name":"Disclosed","at":"2026-11-10T19:17:46.200Z","detail":"C6 NVD published"},{"name":"Scored","at":"2026-11-10T19:17:46.200Z","detail":"CVSS 7.5"},{"name":"Exploited","at":null,"detail":"No exploitation reported"},{"name":"Advisories","at":null,"detail":"None yet"},{"name":"Vendor Response","at":"2026-11-10T18:00:00.000Z","detail":"C41 published"},{"name":"Resolved","at":null,"detail":"After 14 quiet days"}],"signals":[{"at":"2026-11-10T18:00:00.000Z","source":"C41","sourceName":"Red Hat Security Data","role":"Vendor","severity":3,"title":"Red Hat: CVE-2026-105437 (important)","text":"git: git: Heap corruption via integer overflow in merge size calculations","url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-105437.json"},{"at":"2026-11-10T19:17:46.200Z","source":"C6","sourceName":"NVD CVE API 2.0","role":"Database","severity":3,"title":"CVE-2026-105437 (CVSS 7.5)","text":"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…","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105437"},{"at":"2026-11-11T05:53:49.000Z","source":"C31","sourceName":"Vulners (new public exploits)","role":"Research & News","severity":3,"title":"Public exploit: Exploit for CVE-2026-105437","text":"# CVE-2026-105437 — Git three-way merge heap buffer overflow\n\n| | |\n| --- | --- |\n| **CVE** | CVE-2026-105437 |\n| **Component** | Git — three-way merge machinery, `xdiff/xmerge.c` (`xdl_fill_merge_buffer()`) |\n| **Affected** | Git ≤ 2.56.0 (and the 2.50 – 2.55 series) |\n| **Fixed in** | Git…","url":"https://github.com/googlesky/CVE-2026-105437"}],"crowd":[],"reference":{"nvd":{"published":"2026-11-10T19:17:46.200","score":7.5,"severity":"HIGH","desc":"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…","product":"","seen":1794345886420},"kev":null,"epss":null,"p0":false},"mergedInto":null,"publisher":"Event Monitor Cyber"}