CVE-2026-119952: Windows Schannel Remote Code Execution Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Observable timing discrepancy in Windows Schannel allows an unauthorized attacker to execute code over a network.

Description quoted from the CVE record (assigned by microsoft, published 2026-11-10).

Weakness: CWE-208: Observable Timing Discrepancy

How it can be exploited

Exploitable over the network with high attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.

Live scores

EPSS
0.009
low predicted chance of attack
VEDAS
0.045
little exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet

Who is affected

ProductAffectedNot affected
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.9688Not stated
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.9487Not stated
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.7846Not stated
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.7846Not stated
Microsoft Windows 11 version 23H2from 10.0.22631.0 before 10.0.22631.7711Not stated
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.7711Not stated
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.9974Not stated
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.9974Not stated
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.3501Not stated
Microsoft Windows 11 Version 26H2from 10.0.26300.0 before 10.0.26300.9974Not stated
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.9688Not stated
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.9688Not stated
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.9487Not stated
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.9487Not stated
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.5870Not stated
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.33822Not stated
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.33822Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 10.0.14393.9688, 10.0.17763.9487, 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974, 10.0.20348.5870, 10.0.26100.33822.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

Advisories on this CVE

References

Vendor advisories and patches

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust