Skip to content
Fencer Vulns
high 7.5

CVE-2026-50653 json

Azure Active Directory Denial of Service Vulnerability

published 2026-07-14 3 mo ago modified 2026-11-01 7 d ago also EUVD-2026-43782

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

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

Patch / fix

  • Microsoft Azure Active Directory 8.19.2
  • Microsoft Microsoft .NET Framework 3.5 2.0.50727.9182 & 3.0.30729.9168
  • Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8.1 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
  • Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 4.7.4143.0
  • Microsoft Microsoft .NET Framework 4.8 4.8.4803.0
  • Microsoft Microsoft .NET Framework 4.8.1 4.8.9340.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Microsoft Azure Active Directory
  • Microsoft Microsoft .NET Framework 3.5
  • Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8.1
  • Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2
  • Microsoft Microsoft .NET Framework 4.8
  • Microsoft Microsoft .NET Framework 4.8.1

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.