Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach AD FS endpoint over network
-
ExploitSatisfy complexity preconditions (timing/token state)
-
ExecutionBypass weak authentication check
-
ImpactDefeat protected security feature
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Strong authentication
|
| Exploitation Conditions | Requires network reachability to the target's AD FS service (the federation/SSO endpoint); no credentials and no user interaction are needed (PR:N/UI:N), making default-configured, internet-exposed AD FS deployments the primary exposure. The key limiting factor is the CVSS High attack complexity: the description and CWE-1390 (weak authentication) imply the bypass succeeds only under specific, attacker-uncontrolled conditions (such as particular token/request state or timing), not against every request. The precise feature and precondition are not specified in the available data, so defenders should treat externally reachable AD FS instances on pre-patch builds (e.g., Server 2025 <10.0.26100.33650, Server 2022 <10.0.20348.5761, Server 2019 <10.0.17763.9376) as the exposed surface. |
| Impact | This is a moderate-severity (CVSS 5.9) authentication-bypass weakness (CWE-1390) in Microsoft AD FS. The CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N tells a mixed story: the flaw is network-reachable and requires no privileges or user interaction (favoring attackers), but carries High attack complexity, meaning successful exploitation depends on conditions outside the attacker's control (e.g., winning a race, specific token/state, or a non-trivial precondition) - which materially lowers real-world likelihood versus an AC:L bug. Impact is scoped to Integrity only (C:N/I:H/A:N): the attacker bypasses a security feature but does not directly read data or deny service. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is currently no evidence of active exploitation or weaponized exploit code; combined with AC:H, this reads as a genuine but not emergency priority - patch on normal cadence, prioritizing internet-exposed federation endpoints. Note the signals are not conflicting so much as sparse: exploitability metrics are confirmed by the CVSS vector, but exploitation-in-the-wild telemetry (EPSS/KEV/POC) is simply absent rather than negative, so 'low real risk' is inferred from AC:H and missing exploitation signals, not independently confirmed. |
| Exploit ScenarioDerived | An attacker who can reach an organization's AD FS endpoint over the network crafts requests that exploit the weak authentication logic to bypass a security control, under the specific conditions implied by the High attack complexity (e.g., particular timing or token state). No valid credentials and no user interaction are required (PR:N/UI:N). No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Authentication bypass in Microsoft Active Directory Federation Services (AD FS) allows a remote attacker with network reachability to the federation/SSO endpoint to satisfy an authentication check under specific conditions and obtain a trust outcome that should have been denied. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (base 5.9) confirms no credentials and no user interaction are required, while the High attack complexity signals the bypass succeeds only in particular attacker-uncontrolled token or request states rather than against every request; impact is integrity-only (C:N/I:H), meaning a modified or improperly validated authentication decision rather than data disclosure. Microsoft has released vendor fixes for the affected AD FS-enabled Windows Server builds, and no public exploit code or confirmed active exploitation was identified at time of analysis, so risk concentrates on default-configured, internet-exposed, unpatched AD FS deployments.
RemediationAI
Vendor-released patch: Microsoft security updates that raise AD FS-hosting systems to Windows Server 2025 build 10.0.26100.33650, Windows Server 2022 build 10.0.20348.5761, Windows Server 2019 build 10.0.17763.9376, Windows Server 2016 build 10.0.14393.9612, or Windows Server 2012 R2 build 6.3.9600.23470 (with the corresponding Windows 10 1607/1809 updates), as documented at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69982; verify the installed OS build after patching, since the exposure is version-based. Where immediate patching is not possible, treat the AD FS service as untrusted-facing and reduce reachability: block or strictly allow-list inbound 443/TCP to the AD FS farm and its federation proxy endpoints at the perimeter so only known partners and business networks can reach them, accepting the trade-off that legitimate external SSO and partner federation flows must be re-scoped to the new allow-list; front the farm with a WAF/proxy that can inspect SAML/WS-Federation assertions, understanding that this is detection-oriented and cannot fully compensate for a logic flaw in the trust decision; enforce MFA and conditional access at the relying-party layer to blunt successful bypasses, at the cost of requiring step-up enrollment for all users; and alert on anomalous token issuance, unexpected relying-party activity or federation logon events that skip normal claim/MFA requirements, which raises detection confidence but not prevention. Note that no public exploit code was identified at time of analysis, but the absence of a PoC does not reduce the priority of applying the vendor update to internet-exposed AD FS farms.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 11 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
AD FS is the Windows Server role that provides federated identity and single sign-on, consuming and issuing SAML 2.0, WS-Federation and OAuth2/OIDC tokens and acting as the trust anchor between identity providers, relying-party applications and (in hybrid setups) Microsoft Entra ID. The vulnerability is classified as CWE-1390 (Weak Authentication), the root-cause class covering flaws where an authentication mechanism or its verification can be circumvented, here described as a bypass of a security feature. Combined with the assessed vector, the weakness is best understood as an authentication-decision logic gap that is only reachable when a request or token reaches a specific state - consistent with the AC:H rating and with the absence of confidentiality impact, since the attacker manipulates the authentication outcome rather than reading protected data. Affected builds span the Windows Server line that hosts the AD FS role and its OS-level token/federation components: Windows Server 2025 (10.0.26100.x), 2022 (10.0.20348.x), 2019 (10.0.17763.x), 2016 (10.0.14393.x) and 2012 R2 (6.3.9600.x), each in both the full and Server Core installation options, plus Windows 10 1607 and 1809. The CPE/version data supplied by EUVD gives exact remediation thresholds, so exposure is determined by the host OS build rather than by the AD FS configuration alone.
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:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Network-facing AD FS endpoint (AV:N) exploitable without credentials or interaction (PR:N/UI:N), but a security-feature bypass needing specific preconditions (AC:H); impact is integrity-only (I:H, C:N/A:N).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Weak authentication in Active Directory Federation Services (AD FS) allows an unauthorized attacker to bypass a security feature over a network.
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
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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-99667
GHSA-9p3w-qrgm-86ff
NVD
CVE.org
EPSS
Exploit-DB