CVE-2026-50694

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-14) is not newer than that change (2026-11-01), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-44046 (ENISA EUVD) · GHSA-x25h-v5pq-j424 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use after free in Windows Secure Socket Tunneling Protocol (SSTP) allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 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.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

November 1, 2026

Advisory Details (1)

Auto-updated Nov 1, 2026
Patch available. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 95× 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 655 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 555 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-50694?
CVE-2026-50694 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Use after free in Windows Secure Socket Tunneling Protocol (SSTP) allows an unauthorized attacker to execute code over a network.
When was CVE-2026-50694 made public?
CVE-2026-50694 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 November 1, 2026; the record at its source may have been updated since.
Is CVE-2026-50694 actively exploited?
CVE-2026-50694 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50694?
CVE-2026-50694 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-50694?
A fix for CVE-2026-50694 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50694 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50694?

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