CVE-2026-62705

HIGHPre-NVD 7.07.0
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 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 Bind Filter Driver allows an authorized attacker to elevate privileges locally.

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

Published

August 11, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-62705

Vendor Advisories for CVE-2026-62705(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 74× in last 7d / 127× 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 127 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-62705?
CVE-2026-62705 is a high vulnerability published on August 11, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Bind Filter Driver allows an authorized attacker to elevate privileges locally.
When was CVE-2026-62705 disclosed?
CVE-2026-62705 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62705 actively exploited?
CVE-2026-62705 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 91.2% of all scored CVEs.
What is the CVSS score of CVE-2026-62705?
CVE-2026-62705 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62705?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62705, 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-62705

Explore →

Is Your Infrastructure Affected by CVE-2026-62705?

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