CVE-2026-71557

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: 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.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing directory-traversal sequences) can cause go-git to write files outside the intended reference storage directory. Versions 5.19.2 and 6.0.0-alpha.5 fix the issue.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 7, 2026

Last Modified

September 10, 2026

Advisory Details (7)

Auto-updated Aug 7, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v6.0.0-alpha.5

Patch available: go-git/go-git v6.0.0-alpha.5 (pre-release)

https://github.com/go-git/go-git/releases/tag/v6.0.0-alpha.5
github_release Patch Available

v5.19.2

Patch available: go-git/go-git v5.19.2

https://github.com/go-git/go-git/releases/tag/v5.19.2
github_commit Patch Available

commit da9f7d8a0e98 (go-git/go-git)

Patch available: go-git/go-git v6.0.0-alpha.5 (contains commit da9f7d8a0e98)

https://github.com/go-git/go-git/commit/da9f7d8a0e98b475600177348d6ece384a370f36
github_commit Patch Available

commit 4a0e66d555de (go-git/go-git)

Patch available: go-git/go-git v5.19.2 (contains commit 4a0e66d555de)

https://github.com/go-git/go-git/commit/4a0e66d555de5f9a30c31e2df64f445f42bd01e7
github_pr Patch Available

storage: dotgit, reject path traversal in reference names

Patch available: go-git/go-git v5.19.2 (PR #2254 merged 2026-07-17)

https://github.com/go-git/go-git/pull/2254
github_pr Patch Available

storage: dotgit, reject path traversal in reference names

Patch available: go-git/go-git v6.0.0-alpha.5 (PR #2247 merged 2026-07-15)

https://github.com/go-git/go-git/pull/2247
github Patch Available

Malicious reference names may modify files outside the reference storage · Advisory · go-git/go-git · GitHub

https://github.com/go-git/go-git/security/advisories/GHSA-qgq7-7hm3-q39j

Vendor Advisories for CVE-2026-71557(5)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrype-main-0.119.0-0.1.hum12026-09-18redhat
redhatsyft-main-1.52.0-0.1.hum12026-09-18redhat
redhattrivy-main-0.74.0-0.3.hum12026-09-16redhat
redhatkube-state-metrics-main-2.20.0-0.2.hum12026-09-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

(6 across 4 ecosystems)
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, 5.19.1-1
  • every version up to 5.19.2-1: fixed in 5.19.2-1
—
golang-github-go-git-go-git-v66.0.0~alpha.4-1 ... 6~git20260305.2083cf94-3 (7 versions)
  • every version up to 6.0.0~alpha.5-1: fixed in 6.0.0~alpha.5-1
—
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/go-git/go-git/v5—
  • every version up to 5.19.2: fixed in 5.19.2
—
github.com/go-git/go-git/v6—
  • every version up to 6.0.0-alpha.5: fixed in 6.0.0-alpha.5
—
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.

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 15× in last 7d / 69× 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 135 total refreshes for this CVE.

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

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

Same vendor

3 shown

redhat:RHSA-2026:68806 · redhat:RHSA-2026:66208 · redhat:RHSA-2026:68281

Frequently asked(5)

What is CVE-2026-71557?
CVE-2026-71557 is a medium vulnerability published on August 7, 2026. go-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing…
When was CVE-2026-71557 disclosed?
CVE-2026-71557 was first published on August 7, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71557 actively exploited?
CVE-2026-71557 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71557?
CVE-2026-71557 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71557?
A fix for CVE-2026-71557 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71557 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-71557

Explore →

Is Your Infrastructure Affected by CVE-2026-71557?

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

Book a Demo →Browse All CVEs