Git · Out-of-bounds Write
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 3.3 Low.
Data as of 15 Nov 2026, 10:24 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 3.3 |
|---|
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitGit | Affected
| Fixed in– |
AI-suggested
Users should monitor Microsoft Security Response Center advisories for updates.
Description
An out-of-bounds write vulnerability has been identified in Git versions 3.0 and 4.0. This type of vulnerability can lead to memory corruption issues. No CVSS score or detailed impact information is provided. There is no indication of known exploitation in the wild or available patches at this time.