Skip to main content

Microsoft AD FS CVE-2026-83511

| EUVDEUVD-2026-99907 HIGH
Weak Authentication (CWE-1390)
2026-10-13 secure@microsoft.com GHSA-v723-46xp-3rqv
7.4
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach AD FS endpoint over network
  2. Delivery
    Craft spoofed authentication token
  3. Exploit
    Bypass weak token validation
  4. Execution
    Impersonate federated identity
  5. Impact
    Access relying-party application as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Strong authentication
Exploitation Conditions

Requires a deployed AD FS (Active Directory Federation Services) role acting as a federation/identity provider and a network path to its authentication endpoints; exploitation targets the weak authentication logic to spoof a federated identity. The key LIMITING factor is CVSS AC:H: the attacker must satisfy conditions outside their control (such as a specific token-validation state or timing/race condition), which is why CISA SSVC rates the flaw as not Automatable and no exploitation observed. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the High attack complexity substantially reduces the realistic likelihood of reliable, repeatable exploitation compared to a low-complexity bug. Organizations not running the AD FS role are not exposed.

Impact

This is a moderate-severity (CVSS 7.4) spoofing flaw in AD FS stemming from weak authentication (CWE-1390). The signals are mixed and point toward a NON-urgent but genuine risk. On the elevating side: the CVSS vector is network-reachable with no privileges and no user interaction (AV:N/PR:N/UI:N), the stated confidentiality and integrity impact is high (C:H/I:H), and CISA's SSVC rates Technical Impact as 'total'. On the de-escalating side: CVSS attack complexity is High (AC:H), indicating the attacker must satisfy conditions outside their control, and SSVC rates Exploitation as 'none' and Automatable as 'no' - meaning no observed exploitation and no reliable mass-exploitation path. There is NO CISA KEV listing, NO public POC in the provided data, and NO EPSS score was supplied, so exploitation probability cannot be quantified. Net: treat as a real but not emergency priority - patch on a normal-to-expedited cycle rather than as an actively-exploited zero-day. Note one caveat: the description characterizes the outcome as 'spoofing' while the CVSS encodes C:H/I:H/A:N, a combination more typical of token/identity impersonation than data theft - verify the precise impact against the Microsoft advisory before finalizing internal severity.

Exploit ScenarioDerived

A remote, unauthenticated attacker on a network path to an AD FS endpoint exploits the weak authentication to forge or impersonate a federated identity/security token, then authenticates to relying-party applications as another user. Because attack complexity is High (AC:H), success depends on conditions outside the attacker's direct control (e.g., winning a timing/validation condition or a specific token-handling state). No public exploit code was identified in the provided intelligence.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Spoofing of federated identities in Microsoft Active Directory Federation Services (AD FS) lets an unauthenticated network attacker impersonate a federated user by exploiting weak authentication logic (CWE-1390), with high confidentiality and integrity impact but no availability impact (CVSS 7.4). Exploitation requires a deployed AD FS role reachable over the network and is rated high complexity (AC:H) - CISA SSVC records no known exploitation and rates the flaw as not automatable, and no public exploit code has been identified at time of analysis. Organizations that do not run the AD FS server role are not exposed, and Microsoft has released vendor patches for the affected Windows Server builds and the corresponding Windows 10 client builds.

RemediationAI

Apply the Microsoft security update for the Windows build hosting the AD FS role via the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83511); EUVD version ranges indicate the patched build thresholds as 6.3.9600.23470 for Windows Server 2012 R2, 10.0.14393.9612 for Windows Server 2016 / Windows 10 1607, 10.0.17763.9376 for Windows Server 2019 / Windows 10 1809, 10.0.20348.5761 for Windows Server 2022, and 10.0.26100.33650 for Windows Server 2025 - patch status is 'Patch available per vendor advisory', with the exact KB confirmed through the MSRC portal. Where patching must be staged, compensating controls are: restrict inbound TCP 443 to the AD FS farm behind a WAF or reverse proxy and limit extranet exposure to known partner IP ranges (trade-off: legitimate remote and partner SSO traffic must be re-onboarded); require MFA on federated sign-ins and enforce conditional access so a spoofed token alone is insufficient (trade-off: added friction for legacy clients that cannot do MFA); audit and remove unused claims-provider and relying-party trusts so there are fewer trust paths to abuse (trade-off: retires decommissioned but still-referenced partner integrations); and enable high-signal monitoring of AD FS token issuance and 4624/1202-style event logs for anomalous issuer or principal values, since the high attack complexity means a successful spoof is likely to appear as a distinctive, low-volume anomaly rather than a burst of failures. Note that this vulnerability has been assessed as not automatable with no observed exploitation, so these compensating controls are risk-reduction measures rather than a response to active campaigns.

Affected VersionsENISA

Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2019 10.0.17763.0 <10.0.17763.9376

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

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 Microsoft's on-premises security token service and identity provider role, speaking WS-Federation, SAML and OAuth2/OIDC to issue signed tokens to relying-party applications and to consume tokens from partner claims providers. The vulnerability falls under CWE-1390 (Weak Authentication), meaning the token/signature validation or trust-evaluation logic used to establish a federated identity is insufficiently robust, so a crafted request to an authentication endpoint can be accepted as a valid federated principal rather than rejected. The CVSS vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N shows the flaw is reachable over the network by an unauthenticated attacker with no user interaction, but the High attack complexity reflects prerequisites outside the attacker's control (for example a particular token-validation state or timing/race condition), which is consistent with CISA SSVC recording Exploitation: none and Automatable: no. Attackers gain both read and write impact within the security scope of the federated identity context, but the flaw cannot be driven to denial of service. EUVD version ranges confirm exposure is tied to the Windows build hosting the AD FS role rather than to AD FS as a separately versioned product.

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

Vendor (microsoft) PRIMARY 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 7.4 HIGH

Network-reachable federation endpoint with no auth or interaction (AV:N/PR:N/UI:N); AC:H because identity-spoofing needs an out-of-control condition; identity impersonation yields C:H/I:H, no availability impact (A:N).

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:19 cve.org
HIGH 7.4

DescriptionCVE.org

Weak authentication in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

Executive ViewAI

Why It Matters

A spoofing flaw in Microsoft Active Directory Federation Services (AD FS) would let an attacker who can reach a federated AD FS deployment over the network impersonate a federated user, undermining the identity trust that underpins single sign-on across the organization. Only organizations running the AD FS server role on Windows Server are exposed, and Microsoft has released patches for the affected Windows Server and Windows 10 client builds. Because AD FS issues the tokens that grant access to downstream applications and cloud services, successful impersonation could translate into unauthorized access to sensitive data and business systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 53% exploitable
Prevalence
High
AD FS is a widely deployed Microsoft enterprise SSO/federation role across Windows Server
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy