libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API, allowing to build Git functionality into your application. Prior to 1.8.6 and 1.9.5, git_delta_apply in src/libgit2/delta.c trusts the attacker-controlled res_sz value parsed by hdr_sz from a delta object header and passes that amount to git__malloc before validating delta instructions. Malicious pack data supplied through git_clone, git_fetch, git_remote_fetch, git_indexer_append, or a local attacker-supplied repository can use a very small multi-level OFS_DELTA chain to retain extremely large allocations and exhaust memory. This issue is fixed in versions 1.8.6 and 1.9.5.
CVE-2026-53585
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
September 9, 2026
Advisory Details (6)
Auto-updated Aug 20, 2026libgit2 v1.9.5
Patch available: libgit2/libgit2 v1.9.5
https://github.com/libgit2/libgit2/releases/tag/v1.9.5libgit2 v1.8.6
Patch available: libgit2/libgit2 v1.8.6
https://github.com/libgit2/libgit2/releases/tag/v1.8.6commit dec22ac01ad9 (libgit2/libgit2)
Fix landed in libgit2/libgit2 commit dec22ac01ad9 — awaiting tagged release
https://github.com/libgit2/libgit2/commit/dec22ac01ad9620c96b7b9ac3ef636ea46d43bedcommit c1896f06df22 (libgit2/libgit2)
Patch available: libgit2/libgit2 v1.8.6 (contains commit c1896f06df22)
https://github.com/libgit2/libgit2/commit/c1896f06df22cc0ca5658df3a8f6cd7ede4cd6aecommit 0cdfdd5fa8f8 (libgit2/libgit2)
Patch available: libgit2/libgit2 v1.9.5 (contains commit 0cdfdd5fa8f8)
https://github.com/libgit2/libgit2/commit/0cdfdd5fa8f8514c82413025e1e0808866cf7c30Unbounded Memory Allocation via Delta Object Result-Size Header · Advisory · libgit2/libgit2 · GitHub
https://github.com/libgit2/libgit2/security/advisories/GHSA-27m5-gxxh-x79jVendor Advisories for CVE-2026-53585(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libgit2-dev (0.24.1-2ubuntu0.2+esm3) @ xenial | 2026-09-19 | ubuntu |
| redhat | libgit2-main-1.9.7-1.hum1 | 2026-08-25 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libgit2 | 1.5.1+ds-1 ... 1.9.7+ds-1 (32 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libgit2 | 1.9.0+ds-2 | 1.9.0+ds-2+deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libgit2 | 1.9.0+ds-2 ... 1.9.4+ds-1 (13 versions) | 1.9.6+ds-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 17× in last 7d / 80× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 05:01 UTCEG score recompute
- 2026-09-19 05:01 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 04:14 UTCEG score recompute
- 2026-09-18 04:14 UTCVendor advisory
- 2026-09-17 03:28 UTCEG score recompute
- 2026-09-17 03:28 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 02:36 UTCEG score recompute
- 2026-09-16 02:36 UTCVendor advisory
- 2026-09-15 01:49 UTCVendor advisory
- 2026-09-14 01:02 UTCEG score recompute
- 2026-09-14 01:02 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 00:15 UTCEG score recompute
- 2026-09-13 00:15 UTCVendor advisory
- 2026-09-11 23:28 UTCEG score recompute
- 2026-09-11 23:28 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 22:27 UTCEG score recompute
- 2026-09-10 22:27 UTCVendor advisory
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 21:40 UTCVendor advisory
- 2026-09-09 04:15 UTCEG score recompute
Show 55 moreShow fewer
- 2026-09-09 04:15 UTCVendor advisory
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 03:29 UTCEG score recompute
- 2026-09-08 03:29 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 02:43 UTCEG score recompute
- 2026-09-07 02:43 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 01:51 UTCEG score recompute
- 2026-09-06 01:51 UTCVendor advisory
- 2026-09-05 01:02 UTCEG score recompute
- 2026-09-05 01:02 UTCVendor advisory
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-04 00:13 UTCVendor advisory
- 2026-09-02 23:23 UTCEG score recompute
- 2026-09-02 23:23 UTCVendor advisory
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 22:36 UTCEG score recompute
- 2026-09-01 22:36 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 21:49 UTCVendor advisory
- 2026-08-30 21:02 UTCEG score recompute
- 2026-08-30 21:02 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:15 UTCEG score recompute
- 2026-08-29 20:15 UTCVendor advisory
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 19:29 UTCVendor advisory
- 2026-08-27 18:42 UTCEG score recompute
- 2026-08-27 18:42 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:53 UTCEG score recompute
- 2026-08-26 17:53 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 16:26 UTCEG score recompute
- 2026-08-25 16:26 UTCVendor advisory
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:30 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 22:24 UTCEG score recompute
- 2026-08-24 22:24 UTCVendor advisory
- 2026-08-23 21:38 UTCEG score recompute
- 2026-08-23 21:38 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:52 UTCEG score recompute
- 2026-08-22 20:52 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 20:05 UTCVendor advisory
- 2026-08-20 19:18 UTCEG score recompute
- 2026-08-20 19:18 UTCVendor advisory
- 2026-08-20 18:52 UTCEG score recompute
- 2026-08-20 18:52 UTCVendor advisory
- 2026-08-20 18:51 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-53585?
When was CVE-2026-53585 disclosed?
Is CVE-2026-53585 actively exploited?
What is the CVSS score of CVE-2026-53585?
How do I remediate CVE-2026-53585?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53585
Is Your Infrastructure Affected by CVE-2026-53585?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.