CVE-2026-53584

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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.3(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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 computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
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, 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 Patch Available

Submodule path traversal · Advisory · libgit2/libgit2 · GitHub

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

Vendor Advisories for CVE-2026-53584(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 / EcosystemFixed in / PatchReleasedSource
ubuntulibgit2-dev (0.28.4+dfsg.1-2ubuntu0.1+esm1) @ focal2026-09-19ubuntu
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 rangeFixed inDependents
libgit21.5.1+ds-1 ... 1.9.7+ds-1 (32 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libgit21.9.0+ds-21.9.0+ds-2+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libgit21.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 / 83× 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.

  1. 2026-09-19 00:19 UTCEG score recompute
  2. 2026-09-19 00:19 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 00:08 UTCEG score recompute
  5. 2026-09-18 00:08 UTCVendor advisory
  6. 2026-09-16 23:51 UTCEG score recompute
  7. 2026-09-16 23:51 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 23:39 UTCEG score recompute
  11. 2026-09-15 23:39 UTCVendor advisory
  12. 2026-09-14 22:39 UTCVendor advisory
  13. 2026-09-13 22:28 UTCEG score recompute
  14. 2026-09-13 22:28 UTCVendor advisory
  15. 2026-09-13 16:47 UTCEPSS rescore
  16. 2026-09-12 22:17 UTCEG score recompute
  17. 2026-09-12 22:17 UTCVendor advisory
  18. 2026-09-11 22:05 UTCEG score recompute
  19. 2026-09-11 22:05 UTCVendor advisory
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 21:54 UTCEG score recompute
  22. 2026-09-10 21:54 UTCVendor advisory
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-09 21:40 UTCVendor advisory
  25. 2026-09-09 03:48 UTCEG score recompute
Show 58 more
  1. 2026-09-09 03:48 UTCVendor advisory
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-08 03:37 UTCEG score recompute
  4. 2026-09-08 03:37 UTCVendor advisory
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-07 03:25 UTCEG score recompute
  7. 2026-09-07 03:25 UTCVendor advisory
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 03:12 UTCEG score recompute
  10. 2026-09-06 03:12 UTCVendor advisory
  11. 2026-09-05 03:00 UTCEG score recompute
  12. 2026-09-05 03:00 UTCVendor advisory
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-04 02:48 UTCVendor advisory
  15. 2026-09-03 02:29 UTCEG score recompute
  16. 2026-09-03 02:29 UTCVendor advisory
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-02 02:18 UTCEG score recompute
  19. 2026-09-02 02:18 UTCVendor advisory
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-09-01 02:06 UTCVendor advisory
  23. 2026-08-31 01:51 UTCEG score recompute
  24. 2026-08-31 01:51 UTCVendor advisory
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 01:39 UTCEG score recompute
  27. 2026-08-30 01:39 UTCVendor advisory
  28. 2026-08-30 01:22 UTCEPSS rescore
  29. 2026-08-29 01:28 UTCEG score recompute
  30. 2026-08-29 01:28 UTCVendor advisory
  31. 2026-08-28 21:41 UTCEPSS rescore
  32. 2026-08-27 22:06 UTCEG score recompute
  33. 2026-08-27 22:06 UTCVendor advisory
  34. 2026-08-27 14:25 UTCEPSS rescore
  35. 2026-08-26 21:55 UTCEG score recompute
  36. 2026-08-26 21:55 UTCVendor advisory
  37. 2026-08-26 14:46 UTCEPSS rescore
  38. 2026-08-25 21:41 UTCEG score recompute
  39. 2026-08-25 21:41 UTCVendor advisory
  40. 2026-08-25 13:49 UTCEPSS rescore
  41. 2026-08-24 21:07 UTCEG score recompute
  42. 2026-08-24 21:07 UTCVendor advisory
  43. 2026-08-23 20:55 UTCEG score recompute
  44. 2026-08-23 20:55 UTCVendor advisory
  45. 2026-08-23 00:19 UTCEPSS rescore
  46. 2026-08-22 20:43 UTCEG score recompute
  47. 2026-08-22 20:43 UTCVendor advisory
  48. 2026-08-21 23:49 UTCEPSS rescore
  49. 2026-08-21 20:32 UTCVendor advisory
  50. 2026-08-20 20:20 UTCEG score recompute
  51. 2026-08-20 20:20 UTCVendor advisory
  52. 2026-08-20 19:52 UTCEG score recompute
  53. 2026-08-20 19:52 UTCVendor advisory
  54. 2026-08-20 19:18 UTCEG score recompute
  55. 2026-08-20 19:18 UTCVendor advisory
  56. 2026-08-20 18:52 UTCEG score recompute
  57. 2026-08-20 18:52 UTCVendor advisory
  58. 2026-08-20 18:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53584?
CVE-2026-53584 is a medium vulnerability 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 CVE-2026-53584 disclosed?
CVE-2026-53584 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53584 actively exploited?
CVE-2026-53584 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53584?
CVE-2026-53584 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-53584?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53584, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs