CVE-2026-114467: Git · Out-of-bounds Write Possible
Affects gitSource GCVE Database
Not known to be exploited · CVSS 3.3 Low : upgrade to 2.56.1-r0 when convenient.
Data as of 20 Nov 2026, 03:08 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 3.3 |
|---|
- Patch
- Available – fixed in 2.56.1-r0
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 19 Nov 2026.
What to do
Upgrade git to 2.56.1-r0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartgitpkg:apk/cleanstart/gitOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Git to version 2.56.1-r0 or later, where this vulnerability has been fixed. No other mitigation is required as the patch is available and addresses the issue.
Description
An out-of-bounds write vulnerability exists in Git versions prior to 2.56.1-r0 when the git-merge command is used on tags containing more than two GPG signatures. This flaw can cause a denial of service due to application instability.