CVE-2026-50653

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this week

Also known asEUVD-2026-43782 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Loop with unreachable exit condition ('infinite loop') in Azure Active Directory allows an unauthorized attacker to deny service over a network.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.2%
EPSS %ILE
67th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
1.2% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 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-50653

Vendor Advisories for CVE-2026-50653(1)

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 9× in last 7d / 44× 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 261 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 161 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-50653?
CVE-2026-50653 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Loop with unreachable exit condition ('infinite loop') in Azure Active Directory allows an unauthorized attacker to deny service over a network.
When was CVE-2026-50653 made public?
CVE-2026-50653 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-50653 actively exploited?
CVE-2026-50653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50653?
CVE-2026-50653 has a CVSS base score of 7.5 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-50653?
A fix for CVE-2026-50653 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50653 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50653?

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