CVE-2026-53584

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-63546 (ENISA EUVD)Source: ENISA EUVD

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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, libgit2 does not reject traversal components in a submodule path loaded from .gitmodules. The affected src/libgit2/submodule.c paths include git_submodule_lookup and git_submodule_add_setup. A crafted repository can specify a path such as ../escape-target, and applications that initialize the submodule can create directories outside the repository working tree. This issue is fixed in versions 1.8.6 and 1.9.5.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 20, 2026

Last Modified

October 26, 2026

Advisory Details (6)

Auto-updated Aug 20, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

libgit2 v1.9.5

Patch available: libgit2/libgit2 v1.9.5

https://github.com/libgit2/libgit2/releases/tag/v1.9.5
GitHub release Patch Available

libgit2 v1.8.6

Patch available: libgit2/libgit2 v1.8.6

https://github.com/libgit2/libgit2/releases/tag/v1.8.6
GitHub commit Patch Available

commit ec7371da9f35 (libgit2/libgit2)

Patch available: libgit2/libgit2 v1.9.5 (contains commit ec7371da9f35)

https://github.com/libgit2/libgit2/commit/ec7371da9f359cd8293e9108e7a0b1c1b61b67c4
GitHub commit

commit 467c2d95ed66 (libgit2/libgit2)

Fix landed in libgit2/libgit2 commit 467c2d95ed66 — awaiting tagged release

https://github.com/libgit2/libgit2/commit/467c2d95ed663df722f83a5960edf568514b128c
GitHub commit Patch Available

commit 419637d35873 (libgit2/libgit2)

Patch available: libgit2/libgit2 v1.8.6 (contains commit 419637d35873)

https://github.com/libgit2/libgit2/commit/419637d3587396f5d139d6d88480eab3cd81e7a1
GitHub advisoryMentions a patch (unverified)

Submodule path traversal · Advisory · libgit2/libgit2 · GitHub

https://github.com/libgit2/libgit2/security/advisories/GHSA-cw77-j82w-mchm

Vendor Advisories for CVE-2026-53584(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibgit2-fixtures (1.9.1+ds-1ubuntu1.1) @ resolute2026-10-26ubuntu
redhatlibgit2-main-1.9.7-1.hum12026-08-25redhat

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)
PackageVulnerable rangeFix by version rangeDependents
libgit21.5.1+ds-1 ... 1.9.7+ds-1 (32 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libgit21.9.0+ds-2
  • every version up to 1.9.0+ds-2+deb13u1: fixed in 1.9.0+ds-2+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libgit21.9.0+ds-2 ... 1.9.4+ds-1 (13 versions)
  • every version up to 1.9.6+ds-1: fixed in 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 9× in last 7d / 54× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 169 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-26 10:27 UTCEG score recompute
  9. 2026-10-26 10:27 UTCVendor advisory
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-25 14:20 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-10-22 21:48 UTCEG score recompute
  15. 2026-10-22 21:48 UTCVendor advisory
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-10-18 03:31 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
Show 75 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:19 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-09 08:22 UTCEG score recompute
  11. 2026-10-09 08:22 UTCVendor advisory
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-08 05:17 UTCEG score recompute
  14. 2026-10-08 05:17 UTCVendor advisory
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-07 03:49 UTCEG score recompute
  17. 2026-10-07 03:49 UTCVendor advisory
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-06 03:24 UTCVendor advisory
  20. 2026-10-06 03:21 UTCVendor advisory
  21. 2026-10-06 03:21 UTCVendor advisory
  22. 2026-10-06 03:20 UTCEG score recompute
  23. 2026-10-06 03:20 UTCVendor advisory
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  26. 2026-10-04 20:52 UTCVendor advisory
  27. 2026-10-03 16:46 UTCEG score recompute
  28. 2026-10-03 16:46 UTCVendor advisory
  29. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-10-02 08:36 UTCEG score recompute
  32. 2026-10-02 08:36 UTCVendor advisory
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  34. 2026-10-01 08:25 UTCEG score recompute
  35. 2026-10-01 08:25 UTCVendor advisory
  36. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-09-30 08:12 UTCEG score recompute
  38. 2026-09-30 08:12 UTCVendor advisory
  39. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  40. 2026-09-29 03:22 UTCEG score recompute
  41. 2026-09-29 03:22 UTCVendor advisory
  42. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  43. 2026-09-28 03:10 UTCEG score recompute
  44. 2026-09-28 03:10 UTCVendor advisory
  45. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  46. 2026-09-27 02:59 UTCEG score recompute
  47. 2026-09-27 02:59 UTCVendor advisory
  48. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-09-25 01:28 UTCEG score recompute
  50. 2026-09-25 01:28 UTCVendor advisory
  51. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-09-24 01:16 UTCVendor advisory
  53. 2026-09-23 01:05 UTCEG score recompute
  54. 2026-09-23 01:05 UTCVendor advisory
  55. 2026-09-22 00:54 UTCEG score recompute
  56. 2026-09-22 00:54 UTCVendor advisory
  57. 2026-09-21 00:42 UTCEG score recompute
  58. 2026-09-21 00:42 UTCVendor advisory
  59. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  60. 2026-09-20 00:30 UTCEG score recompute
  61. 2026-09-20 00:30 UTCVendor advisory
  62. 2026-09-19 00:19 UTCEG score recompute
  63. 2026-09-19 00:19 UTCVendor advisory
  64. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  65. 2026-09-18 00:08 UTCEG score recompute
  66. 2026-09-18 00:08 UTCVendor advisory
  67. 2026-09-16 23:51 UTCEG score recompute
  68. 2026-09-16 23:51 UTCVendor advisory
  69. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  70. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  71. 2026-09-15 23:39 UTCEG score recompute
  72. 2026-09-15 23:39 UTCVendor advisory
  73. 2026-09-14 22:39 UTCVendor advisory
  74. 2026-09-13 22:28 UTCEG score recompute
  75. 2026-09-13 22:28 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53584?
CVE-2026-53584 is a medium-severity vulnerability; its CVE record was published on August 20, 2026. 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, libgit2 does not reject traversal components in a submodule path loaded from .gitmodules. The affected…
When was the CVE record for CVE-2026-53584 published?
The CVE record for CVE-2026-53584 was published on August 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-53584 actively exploited?
CVE-2026-53584 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53584?
CVE-2026-53584 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53584?
A fix for CVE-2026-53584 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53584 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53584

Explore →

Is Your Infrastructure Affected by CVE-2026-53584?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs