CVE-2026-114467: Stack Memory Corruption in Git Signed-Tag Merging
CVE-2026-114467 is an out-of-bounds write vulnerability in Git's remove_signature() function. When stripping GPG signatures from messages, the function stores signature boundaries in a fixed-size stack array that accommodates only two signatures. Processing a message containing more than two signatures writes beyond the array and corrupts stack memory. Merging a specially crafted tag can trigger the vulnerability, potentially crashing Git and causing denial of service.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can corrupt stack memory and terminate the Git process performing a merge. This can disrupt local merge operations or server-side merge workflows on repository hosting services that process attacker-supplied tags. Arbitrary code execution and confidentiality impacts are not established for this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid git merge operations involving signed tags, particularly tags from untrusted sources. On hosting services, restrict or temporarily disable workflows that merge user-supplied signed tags. These precautions do not replace installing the security update.
Remediation
Patch, then assume compromise.
Upgrade to Git 2.56.1 or an applicable patched maintenance release: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, or 2.50.2. Alternatively, install a distributor-provided package containing the fix. The patch rewrites remove_signature() to handle multiple signatures safely. Update bundled Git copies and Git installations used by repository hosting services and automation.
Exploits
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Frequently asked questions
- Is CVE-2026-114467 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-114467 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-114467?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-114467.
- Is there a patch for CVE-2026-114467?
- Upgrade to Git 2.56.1 or an applicable patched maintenance release: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, or 2.50.2. Alternatively, install a distributor-provided package containing the fix.
- How severe is CVE-2026-114467?
- CVE-2026-114467 has a CVSS v3.1 score of 3.3 (Low) and an EPSS score of 0.22% (13th percentile) as of Nov 17, 2026.
Recent activity
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.