CVE-2026-50653 — Azure Active Directory Denial of Service Vulnerability
Loop with unreachable exit condition ('infinite loop') in Azure Active Directory allows an unauthorized attacker to deny service over a network.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — msrc.microsoft.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Microsoft .net Framework, Microsoft Azure Active Directory, Microsoft Microsoft .NET Framework 3.5…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Microsoft | .net Framework | version 3.5version 4.8.1version 4.6.2version 4.7version 4.7.1version 4.7.2version 4.8 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Azure Active Directory | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Azure Active Directory | ≥ 2021 and < 8.19.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 3.5 | ≥ 3.5.0 and < 2.0.50727.9182 & 3.0.30729.9168 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.7.2 | ≥ 4.7.0 and < 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.8 | ≥ 4.8.0 and < 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.8.1 | ≥ 4.8.1 and < 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 | ≥ 4.7.0 and < 4.7.4143.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 4.8 | ≥ 4.8.0 and < 4.8.4803.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft .NET Framework 4.8.1 | ≥ 4.8.0.0 and < 4.8.9340.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | secure@microsoft.com via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | microsoft via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: secure@microsoft.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · microsoft/azure active directory, microsoft/microsoft .net framework 3.5, microsoft/microsoft .net framework 3.5 and 4.7
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 7.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-97801 .NET Framework Tampering Vulnerability 2d
- High CVE-2026-97788 Active Directory Federation Services (AD FS) Information Disclosure Vulnerability 2d
- High CVE-2026-96958 .NET Denial of Service Vulnerability 2d
- High CVE-2026-96959 .NET Denial of Service Vulnerability 2d
- High CVE-2026-96960 .NET Denial of Service Vulnerability 2d
- High CVE-2026-96233 ASP.NET Core Denial of Service Vulnerability 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-50653 is "Azure Active Directory Denial of Service Vulnerability", rated High. It affects .net Framework (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.