Skip to main content
Mallory
MediumVulnerability

CVE-2026-114469: Out-of-bounds read in Git binary patch application

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days22 mentions · peak 7 in a dayToday
CVSS4.4Medium · v3.1
EPSS0.24%16th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-114469CWE-125 · Out-of-bounds Read

CVE-2026-114469 is an out-of-bounds read vulnerability in Git's binary patch application functionality. Git enforces an approximately 1 GiB patch-size limit against the compressed and encoded input without adequately validating the expanded size. A crafted binary patch can therefore pass the input-size check while expanding far beyond the limit. During application, a truncated delta size can exceed the actual buffer length, triggering an out-of-bounds read in patch_delta() and crashing Git.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

An attacker-supplied binary patch can crash the Git process applying it, causing denial of service and disrupting patch-processing workflows or automation. Code execution, information disclosure, and integrity compromise are not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid applying binary patches from untrusted sources and prevent automated workflows from processing externally supplied binary patches. Restricting only the compressed or encoded input size does not address the expanded-size validation flaw. These precautions do not replace installing the fix.

Remediation

Patch, then assume compromise.

Upgrade to Git 2.56.1 or the patched maintenance release for the installed series: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, or 2.50.2. Alternatively, install the operating-system vendor's security update containing the fix. Update applications that bundle Git and Git installations used by automation or services processing external patches. The fix additionally validates the declared uncompressed binary-patch size and rejects patches exceeding MAX_APPLY_SIZE.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-114469 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-114469 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-114469?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-114469.
Is there a patch for CVE-2026-114469?
Upgrade to Git 2.56.1 or the patched maintenance release for the installed series: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, or 2.50.2. Alternatively, install the operating-system vendor's security update containing the fix.
How severe is CVE-2026-114469?
CVE-2026-114469 has a CVSS v3.1 score of 4.4 (Medium) and an EPSS score of 0.24% (16th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.