Azure Active Directory Denial of Service Vulnerability
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Azure Active Directory 5.7.1, 7.7.3, 8.19.2; Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for 32-bit Systems 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0; Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for x64-based Systems 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0.
Low priority for now. Upgrade to Azure Active Directory 5.7.1, 7.7.3, 8.19.2; Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for 32-bit Systems 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0; Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for x64-based Systems 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Deserialization of untrusted data in Azure Active Directory allows an unauthorized attacker to deny service over a network.
- Published
- Jul 14, 2026
- Updated
- Oct 8, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-502
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | .net framework | cpe:2.3:a:microsoft:.net_framework |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 21h2 | cpe:2.3:o:microsoft:windows_10_21h2 |
| microsoft | windows 10 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows 11 24h2 | cpe:2.3:o:microsoft:windows_11_24h2 |
| microsoft | windows 11 25h2 | cpe:2.3:o:microsoft:windows_11_25h2 |
| microsoft | windows 11 26h1 | cpe:2.3:o:microsoft:windows_11_26h1 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft azure active directoryall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Azure Active Directory
- 2021 and later · before 5.7.1affected
Microsoft Microsoft .NET Framework 3.5
- 3.5.0 and later · before 2.0.50727.9182 & 3.0.30729.9168affected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
- 4.7.0 and later · before 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8
- 4.8.0 and later · before 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8.1
- 4.8.1 and later · before 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0affected
Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2
- 4.7.0 and later · before 4.7.4143.0affected
Microsoft Microsoft .NET Framework 4.8
- 4.8.0 and later · before 4.8.4803.0affected
Microsoft Microsoft .NET Framework 4.8.1
- 4.8.0.0 and later · before 4.8.9340.0affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-0646A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote KEV99Now
- CVE-2024-29059.NET Framework Information Disclosure VulnerabilityKEV90Now
- CVE-2017-8759Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious documeKEV88Now
- CVE-2015-1671The Windows DirectWrite library, as used in Microsoft .NET Framework 3.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2; Office 2007 SP3 and 2010KEV76This week
- CVE-2023-36899ASP.NET Elevation of Privilege Vulnerability58Plan
- CVE-2014-0257Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine whether it is safe to execute 58Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Azure Active Directory | 5.7.1 · Release Notes | Microsoft (MSRC) |
| Azure Active Directory | 7.7.3 · Release Notes | Microsoft (MSRC) |
| Azure Active Directory | 8.19.2 · Release Notes | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for 32-bit Systems | 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0 · KB5099535 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for x64-based Systems | 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0 · KB5099535 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems | 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0 · KB5100989 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems | 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0 · KB5100989 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2016 | 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0 · KB5099535 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2016 (Server Core installation) | 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0 · KB5099535 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 | 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0 · KB5100989 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation) | 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0 · KB5100989 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems | 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0 · KB5101008 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems | 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0 · KB5101008 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for 32-bit Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101006 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for ARM64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101006 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for x64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101006 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for 32-bit Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101006 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for ARM64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101006 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for x64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101006 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 | 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0 · KB5101008 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation) | 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0 · KB5101008 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022 | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101010 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022 (Server Core installation) | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0 · KB5101010 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for 32-bit Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101000 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for ARM64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101000 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for x64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101000 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for 32-bit Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101000 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for ARM64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101000 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for x64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101000 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 23H2 for ARM64-based Systems | 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0 · KB5101004 | Microsoft (MSRC) |
+27
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-506460 days apart.NET Framework Remote Code Execution Vulnerability32Monitor
- CVE-2026-506490 days apart.NET Remote Code Execution Vulnerability32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)job = pickle.loads(payload)Fixed
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig): raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.