CVE-2026-50364

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. The CNA's CVSS baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper link resolution before file access ('link following') in Windows Server Backup allows an authorized attacker to elevate privileges locally.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2026-50364(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 330 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 230 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50364?
CVE-2026-50364 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Improper link resolution before file access ('link following') in Windows Server Backup allows an authorized attacker to elevate privileges locally.
When was CVE-2026-50364 made public?
CVE-2026-50364 was made public on July 14, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-50364 actively exploited?
CVE-2026-50364 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50364?
CVE-2026-50364 has a CVSS base score of 7.3 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-50364?
A fix for CVE-2026-50364 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50364 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50364?

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

Book a Demo →Browse All CVEs