CVE-2026-56649

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

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

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Network File System allows an unauthorized attacker to execute code over a network.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
47.5%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-56649

Vendor Advisories for CVE-2026-56649(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 31× 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-07-25 14:18 UTCEPSS rescore
  2. 2026-07-25 14:18 UTCEPSS rescore
  3. 2026-07-24 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:20 UTCEG score recompute
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 02:48 UTCEG score recompute
  12. 2026-07-19 02:48 UTCVendor advisory
  13. 2026-07-19 02:48 UTCGHSA enrichment
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-17 14:05 UTCEG score recompute 2.20
  17. 2026-07-17 14:05 UTCVendor advisory
  18. 2026-07-17 14:05 UTCGHSA enrichment
  19. 2026-07-17 14:00 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  20. 2026-07-17 07:29 UTCEG score recompute
  21. 2026-07-17 07:29 UTCVendor advisory
  22. 2026-07-17 07:29 UTCGHSA enrichment
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-16 15:07 UTCGHSA enrichment
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 6 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:25 UTCVendor advisory
  3. 2026-07-15 16:24 UTCGHSA enrichment
  4. 2026-07-14 17:42 UTCEG score recompute
  5. 2026-07-14 17:42 UTCVendor advisory
  6. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56649?
CVE-2026-56649 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Network File System allows an unauthorized attacker to execute code over a network.
When was CVE-2026-56649 disclosed?
CVE-2026-56649 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56649 actively exploited?
CVE-2026-56649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 47.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56649?
CVE-2026-56649 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-56649?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56649, 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-56649

Explore →

Is Your Infrastructure Affected by CVE-2026-56649?

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