CVE-2026-58598

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. 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 Backup Engine allows an authorized attacker to elevate privileges locally.

CVSS v3
7.0
EG Score
7.0(medium)
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

July 16, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Jul 16, 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-58598

Vendor Advisories for CVE-2026-58598(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 24× in last 7d / 136× 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 271 total refreshes for this CVE.

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58598?

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