CVE
Git out-of-bounds read in binary patch processing
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.24% · 15th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Git is affected by an out-of-bounds read bug that can crash the git-apply command when it processes a binary patch that inflates to a very large size. An attacker would need local access and must get a user to take an action, such as running git-apply on a crafted patch.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Out-of-bounds read can crash git-apply(1) when binary patch inflates to very large size
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.4/10CVSS 4.4
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-114469 (Out-of-bounds Read in Git), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-114469 (entry last updated 2026-11-12):
Affected:
- Git Git: versions 2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-114469 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114469 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.com/gitlab-org/git/-/work_items/811
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-114469
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114469"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Git Git
2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-114469
Is CVE-2026-114469 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-114469?
Git: versions 2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0 and 2 more.Source: cve.now feed data