CVE-2026-45571

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

go-git is an extensible git implementation library written in pure Go. Prior to 5.19.1 and 6.0.0-alpha.4, a path validation issue in go-git could allow crafted repository data to affect files outside the intended checkout target, including the repository's .git directory. These validations were introduced in upstream Git years ago, so the vulnerability arose from go-git drifting from those checks. This vulnerability is fixed in 5.19.1 and 6.0.0-alpha.4.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

May 19, 2026

Last Modified

June 4, 2026

Advisory Details (1)

Auto-updated Jun 16, 2026
Patch available. Sources: github.
github Patch Available

Crafted repositories may modify main and submodule .git directories · Advisory · go-git/go-git · GitHub

https://github.com/go-git/go-git/security/advisories/GHSA-crhj-59gh-8x96

Vendor Advisories for CVE-2026-45571(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat

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

(7 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/go-git/go-git———
github.com/go-git/go-git/v5—5.19.1—
github.com/go-git/go-git/v6—6.0.0-alpha.4—
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-git5.14.0-1, 5.16.2-1, 5.17.0-1, 5.17.1-15.19.1-1—
golang-github-go-git-go-git-v66~git20260305.2083cf94-1, 6~git20260305.2083cf94-2, 6~git20260305.2083cf94-36.0.0~alpha4-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-git5.11.0-1 ... 5.4.2-4 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-git5.14.0-1, 5.16.2-1, 5.17.0-1, 5.17.1-1, 5.19.1-1——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 62× 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.

Showing the most recent 100 of 142 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45571?
CVE-2026-45571 is a medium vulnerability published on May 19, 2026. go-git is an extensible git implementation library written in pure Go. Prior to 5.19.1 and 6.0.0-alpha.4, a path validation issue in go-git could allow crafted repository data to affect files outside the intended checkout target, including the repository's .git directory. These validations were…
When was CVE-2026-45571 disclosed?
CVE-2026-45571 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on June 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45571 actively exploited?
CVE-2026-45571 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 78.3% of all scored CVEs.
What is the CVSS score of CVE-2026-45571?
CVE-2026-45571 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-45571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45571, 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-45571

Explore →

Is Your Infrastructure Affected by CVE-2026-45571?

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

Start Free Scan →Browse All CVEs