Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Gain man-in-the-middle network position
  2. Delivery
    Intercept Schannel TLS handshake
  3. Exploit
    Exploit spoofing flaw to forge server identity
  4. Execution
    Establish trusted session with victim
  5. Impact
    Intercept or tamper with protected traffic

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Anti-spoofing controls
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to occupy a privileged position on the network path between client and server to interfere with a Schannel-negotiated TLS session (consistent with AV:N combined with AC:H and the 'spoofing over a network' description); it does not require authentication (PR:N) or user interaction (UI:N). The practical limiting factor is achieving that man-in-the-middle or on-path position and satisfying the specific handshake/timing conditions implied by AC:H, which prevents straightforward opportunistic exploitation against arbitrary remote targets. Exact affected Windows versions and whether any non-default TLS/cipher configuration is required are not specified in the available data and should be confirmed in the MSRC advisory.

Impact

Microsoft rates this Windows Schannel spoofing flaw at CVSS 9.0 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), meaning network-reachable and unauthenticated (PR:N) but with high attack complexity (AC:H) and a scope change (S:C) propagating full confidentiality, integrity, and availability impact beyond the vulnerable component. The high score is driven almost entirely by the triple-High impact plus scope change rather than by ease of exploitation - AC:H signals a meaningful precondition such as a privileged network position, a race, or specific handshake timing, which tempers the real-world likelihood versus a trivially remote bug. No EPSS score, CISA KEV listing, or public POC was provided, so there is no current evidence of active or imminent exploitation; the risk at this moment is latent rather than demonstrated. Two signals warrant caution and verification: the CWE is 'N/A' (no weakness classification), and a conflict exists in the metadata - the impact subscores (C:H/I:H/A:H) are unusually broad for a vulnerability labeled strictly as 'spoofing,' which typically maps to integrity impact; confirm the exact impact profile against the Microsoft advisory. Given Schannel's role as the core Windows TLS/SSL provider, a confirmed exploitable spoofing/MITM primitive here would be a genuine priority, but the AC:H gate and absence of exploitation signals place it below trivially-exploitable, actively-exploited bugs in patching order.

Exploit ScenarioDerived

An attacker positioned on the network path (e.g., via ARP/DNS poisoning or a rogue access point) interferes with a Schannel-protected TLS session and exploits the flaw to spoof a trusted server identity or manipulate the handshake, causing the victim client to establish a session it believes is authentic. This enables interception or tampering of ostensibly secure traffic. No public exploit is identified, and the AC:H rating indicates the attacker must achieve a privileged network position and meet specific handshake conditions to succeed.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
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 13, 2026

Spoofing in Windows Schannel allows an unauthenticated attacker positioned on the network path between a client and server to interfere with TLS session establishment, potentially bypassing authentication and compromising confidentiality and integrity. Microsoft rates this CVSS 9.0, while our independent assessment assigns a modified vector with no availability impact (A:N) and notes that exploitation requires high attack complexity (AC:H) due to the need for a man-in-the-middle position and specific handshake/timing conditions. No public exploit identified at time of analysis.

RemediationAI

No specific patch version is provided in the available data; consult the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-105008 for updates and apply the security update once available. If a patch is not yet deployed, consider mitigating by enforcing mutual TLS (mTLS) to authenticate both endpoints, which can prevent spoofing if the attacker cannot present a valid client certificate; however, this requires configuration on both client and server and may impact compatibility. Alternatively, use network segmentation and IPsec to protect the path between clients and servers, though this adds overhead. Monitoring for anomalous TLS handshake failures may help detect exploitation attempts. Vendor-released patch status is not confirmed from the provided data.

Affected VersionsENISA

Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
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_2012_server_core_installation fix: 6.2.9200.26434
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 20 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Windows Schannel is Microsoft's implementation of the TLS/SSL protocols, responsible for secure communications in Windows. The vulnerability is an authentication bypass via spoofing, likely stemming from improper validation during the TLS handshake, allowing an on-path attacker to impersonate a legitimate endpoint. The root cause class is not specified (CWE N/A), but the CVSS vector indicates a scope change (S:C) and high confidentiality and integrity impact, while availability is not impacted per our assessment (A:N). The attack requires a privileged network position and specific handshake/timing conditions (AC:H).

Know when Windows 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 9.0 CRITICAL
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 8.7 HIGH

Network-reachable spoofing needing an on-path position justifies AV:N/AC:H/PR:N; a broken TLS channel breaks C and I with scope change (S:C), but no clear availability impact (A:N).

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:17 nvd
CRITICAL 9.0

DescriptionCVE.org

No cwe for this issue in Windows Schannel allows an unauthorized attacker to perform spoofing over a network.

Executive ViewAI

Why It Matters

A critical spoofing vulnerability in Microsoft Windows Schannel, the core TLS/SSL implementation, could allow attackers to bypass authentication and compromise the confidentiality and integrity of encrypted communications. This affects all Windows systems using Schannel for secure connections, potentially exposing sensitive data and undermining trust in network security. With no vendor-released patch identified at time of analysis and a critical severity rating, leadership should prioritize immediate risk assessment and mitigation.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include enforcing network segmentation to restrict man-in-the-middle positioning, implementing certificate pinning and mutual TLS authentication where feasible, and monitoring for anomalous TLS handshake behavior. Additionally, restrict access to trusted networks and apply least privilege.

Threat Intelligence Overview

EPSS Score
0.6%
Top 53% exploitable
Prevalence
Ubiquitous
Schannel is the native TLS/SSL provider in every Windows installation
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
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
Very High
Technical Impact
Total

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +45
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

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

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

CVE-2026-96951 HIGH POC
8.8 Oct 13

Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then

CVE-2025-24054 MEDIUM POC
6.5 Mar 11

External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network

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