CVE-2026-62960

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Git for Windows is the Windows port of Git. Prior to 2.55.0.windows.4, a malicious remote Git server can advertise a bundle URI that reaches transport_get_remote_bundle_uri(), fetch_bundle_uri_internal(), and copy_uri_to_file() in bundle-uri.c during clone or fetch when transfer.bundleuri=true. Non-HTTP(S) values are treated as local filesystem paths, and file URI prefixes are removed, so a bare UNC path or file URI targeting an attacker-controlled share causes Windows to initiate an outbound SMB connection. This can expose NTLM authentication material to the attacker-selected host. This issue is fixed in version 2.55.0.windows.4.

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

Published

August 21, 2026

Last Modified

August 21, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Server-advertised bundle-uri can trigger outbound SMB callbacks via UNC and file:// paths on Windows · Advisory · git-for-windows/git · GitHub

https://github.com/git-for-windows/git/security/advisories/GHSA-xrpg-8j9v-v282
github_release Patch Available

Git for Windows 2.55.0(4)

Patch available: git-for-windows/git v2.55.0.windows.4

https://github.com/git-for-windows/git/releases/tag/v2.55.0.windows.4
github_commit

commit a93524749d78 (git-for-windows/git)

Fix landed in git-for-windows/git commit a93524749d78 — awaiting tagged release

https://github.com/git-for-windows/git/commit/a93524749d7806870fd2b4b00a3812da1d6e5f4a

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-08-25 19:10 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 19:28 UTCEG score recompute
  4. 2026-08-23 07:55 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 20:23 UTCEG score recompute
  7. 2026-08-21 20:10 UTCEG score recompute
  8. 2026-08-21 20:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62960?
CVE-2026-62960 is a high vulnerability published on August 21, 2026. Git for Windows is the Windows port of Git. Prior to 2.55.0.windows.4, a malicious remote Git server can advertise a bundle URI that reaches transportgetremotebundleuri(), fetchbundleuriinternal(), and copyuritofile() in bundle-uri.c during clone or fetch when transfer.bundleuri=true. Non-HTTP(S)…
When was CVE-2026-62960 disclosed?
CVE-2026-62960 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62960 actively exploited?
CVE-2026-62960 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 71.2% of all scored CVEs.
What is the CVSS score of CVE-2026-62960?
CVE-2026-62960 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-62960?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62960, 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

Explore the affected products and dependency analysis for CVE-2026-62960

Explore →

Is Your Infrastructure Affected by CVE-2026-62960?

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

Start Free Scan →Browse All CVEs