Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach AD FS endpoint over network
-
ExploitSend crafted request triggering oversized allocation
-
ExecutionMemory exhaustion in AD FS service
-
ImpactService crash denies federated authentication
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory allocation limits
|
| Exploitation Conditions | Requires a reachable AD FS (Active Directory Federation Services) role endpoint on an affected Windows Server build (e.g., Server 2016/2019/2022/2025 and Server Core variants prior to the listed patched builds); the AD FS role must be installed and network-accessible to the attacker. No authentication, privileges, or user interaction are needed (PR:N/UI:N), so default AD FS deployments exposed to the attacker's network are at risk. Limiting factors: organizations that do not run the AD FS role are unaffected, and exposure is reduced where AD FS endpoints are restricted to internal networks or fronted by a Web Application Proxy / filtering layer; impact is confined to availability (service disruption), with no data exposure or code execution. |
| Impact | All signals converge on this being a genuine but moderate-priority availability issue rather than a critical breach risk. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) describes a network-reachable, low-complexity, unauthenticated denial of service with impact strictly on availability - there is no confidentiality or integrity loss, which caps the score at 7.5/HIGH. This is corroborated by CWE-789 (memory allocation with excessive size) and the description, both of which point to a resource-exhaustion DoS, not code execution or data compromise. SSVC reinforces a measured posture: Exploitation is 'none' (no observed or public exploitation), Automatable is 'yes' (consistent with a scriptable unauthenticated network request), and Technical Impact is 'partial' (service disruption, not full control). There is no CISA KEV listing and no POC identified, and no EPSS score was supplied in the input, so exploitation probability cannot be quantified from this data. Note the conflict to flag: the input Tag 'Authentication Bypass' directly contradicts the CVSS impact metrics (C:N/I:N/A:H) and the description - this is a pure availability DoS, not an auth bypass, so that tag should be disregarded. Net: a real patch-worthy issue for AD FS operators given the unauthenticated network vector, but lower urgency than any flaw carrying confidentiality/integrity impact or active exploitation. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a specially crafted request to an internet- or network-reachable AD FS endpoint that causes the service to allocate an excessively large amount of memory, exhausting resources and crashing or hanging the federation service. Because AD FS brokers single sign-on, a successful DoS can block authentication for all federated applications until the service recovers. No public exploit identified at time of analysis, and SSVC lists exploitation as 'none'. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated network requests to a reachable Active Directory Federation Services (AD FS) endpoint on unpatched Windows Server builds can drive excessive memory allocation and exhaust the service's resources, denying service to legitimate users. The vulnerability carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials, privileges, or user interaction are required, but the impact is confined to availability - no confidentiality or integrity loss and no code execution. CISA's SSVC assessment records exploitation as 'none' and no public exploit code has been identified at time of analysis, so this is a genuine but moderate-priority availability risk for organizations that actually run the AD FS role; Microsoft has published fixed builds for the affected Windows Server 2012 through 2025 and Server Core platforms.
RemediationAI
Apply the Microsoft security update for CVE-2026-85324 from the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85324) and confirm the host reaches the fixed build for its branch - 6.2.9200.26434 (Server 2012), 6.3.9600.23470 (2012 R2), 10.0.14393.9612 (2016), 10.0.17763.9376 (2019), 10.0.20348.5761 (2022), or 10.0.26100.33650 (2025); this is the vendor-released fix and no separate AD FS component patch is required. Prioritize any server that actually hosts the AD FS role, since unpatched hosts without the role are not exposed through this path; if the role is unused, removing it eliminates the attack surface outright. Until patching completes, compensating controls are worth their trade-offs: restrict AD FS endpoint access (HTTPS/443) to trusted internal networks or front the service with a Web Application Proxy or reverse proxy and apply request-size and rate limits there - at the cost of potential latency or blocked legitimate sign-in traffic if the limits are too aggressive - and place AD FS behind network filtering so only known client networks reach /adfs/ls rather than the public internet. Continuous memory monitoring on the AD FS host with a supervised service restart can shorten the duration of a disruption, but it is only a stopgap because an attacker can simply repeat the request; the update remains the only durable fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-789 (Memory Allocation with Excessive Size Value), an uncontrolled-resource-consumption class in which a crafted request causes the AD FS service to allocate far more memory than the workload warrants, leading to memory exhaustion or process failure rather than memory-corruption exploitation. AD FS is the Windows Server role that brokers SAML/WS-Federation/OIDC token issuance for federated identity, and its endpoints (notably /adfs/ls and the federation metadata and token endpoints) are designed to be reachable by unauthenticated clients during sign-in flows - which is exactly why the assessed vector is PR:N/UI:N and why an exposed role instance is enough to trigger the condition. The EUVD data shows the flaw tracked across the Windows Server servicing branches: Windows Server 2012 (6.2.9200.0), 2012 R2 (6.3.9600.0), 2016 (10.0.14393.0), 2019 (10.0.17763.0), 2022 (10.0.20348.0) and 2025 (10.0.26100.0), including the Server Core installation variants, plus the matching Windows 10 1607 (10.0.14393.0) and 1809 (10.0.17763.0) client branches that share those build lineages. Note one data inconsistency worth flagging: the supplied tag 'Authentication Bypass' is not supported by the description, the CWE, or the assessed vector - the verified impact is availability only (C:N/I:N/A:H), and no bypass of authentication has been demonstrated, so defenders should not treat this as a credential or session-integrity issue.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Unauthenticated network-reachable AD FS endpoint (AV:N/PR:N/UI:N) with low-complexity resource exhaustion causing service outage only, so C:N/I:N/A:H.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Memory allocation with excessive size value in Active Directory Federation Services (AD FS) allows an unauthorized attacker to deny service over a network.
Executive ViewAI
A high-severity availability flaw in the Active Directory Federation Services (AD FS) role on unpatched Windows Server builds could let any unauthenticated party on the network overwhelm the service and knock it offline, cutting off sign-in for every application that depends on it. Organizations that have not deployed the vendor's fixed Windows Server builds (2012 through 2025 and Server Core) face a denial-of-service risk against a tier-zero authentication service, which can halt access to email, SaaS, and line-of-business applications for the entire workforce. No public exploit code or active exploitation has been observed, so this is a manageable, patch-driven risk rather than an emergency, but remediation should be prioritized because AD FS outages have an immediate and organization-wide blast radius.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-99464
GHSA-v84j-m79w-hg8h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB