CVE-2026-45570

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% 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, nvd
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.6Exploit: None knownExposed services: Not assessed

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, go-git's SSH transport constructs the remote exec command by wrapping the repository path in single quotes without escaping single quotes embedded inside the path. A repository path containing a single quote can therefore break out of the quoted region in the exec command and be appended as additional shell tokens. This vulnerability is fixed in 5.19.1 and 6.0.0-alpha.4.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

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
Severity96% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

Published

May 19, 2026

Last Modified

June 4, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Improper single-quote escaping in go-git SSH transport · Advisory · go-git/go-git · GitHub

https://github.com/go-git/go-git/security/advisories/GHSA-m7cr-m3pv-hgrp

Vendor Advisories for CVE-2026-45570(3)

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

Affected Packages

(7 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/go-git/go-git—
  • every version through 4.7.0: no fix on record
  • every version on: no fix on record
—
github.com/go-git/go-git/v5—
  • every version up to 5.19.1: fixed in 5.19.1
—
github.com/go-git/go-git/v6—
  • every version up to 6.0.0-alpha.4: fixed in 6.0.0-alpha.4
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-git-go-git5.14.0-1, 5.16.2-1, 5.17.0-1, 5.17.1-1
  • every version up to 5.19.1-1: fixed in 5.19.1-1
—
golang-github-go-git-go-git-v66~git20260305.2083cf94-1, 6~git20260305.2083cf94-2, 6~git20260305.2083cf94-3
  • every version up to 6.0.0~alpha4-1: fixed in 6.0.0~alpha4-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-git-go-git5.11.0-1 ... 5.4.2-4 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-git-go-git5.14.0-1 ... 5.19.2-1 (6 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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 218 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45570?
CVE-2026-45570 is a critical 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, go-git's SSH transport constructs the remote exec command by wrapping the repository path in single quotes without escaping single quotes embedded inside the path. A repository path containing…
When was CVE-2026-45570 disclosed?
CVE-2026-45570 was first published 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-45570 actively exploited?
CVE-2026-45570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45570?
CVE-2026-45570 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-45570?
A fix for CVE-2026-45570 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45570 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-45570

Explore →

Is Your Infrastructure Affected by CVE-2026-45570?

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

Book a Demo →Browse All CVEs