Skip to main content
Vulnerability Database/CVE-2026-105005

CVE-2026-105005: Windows Schannel RCE Vulnerability

CVE-2026-105005 is an out-of-bounds write vulnerability in Windows Schannel that enables remote code execution over a network. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-105005 Overview

CVE-2026-105005 is an out-of-bounds write vulnerability [CWE-787] in Windows Secure Channel (Schannel), the Microsoft implementation of SSL/TLS used across Windows networking stacks. An unauthenticated remote attacker can trigger memory corruption during protocol processing and execute code on the target system.

The flaw carries a CVSS 3.1 base score of 8.1 and does not require user interaction or prior privileges. Microsoft published the advisory in the Microsoft Security Update Guide. No public proof-of-concept or in-the-wild exploitation has been confirmed at the time of writing.

Critical Impact

Remote code execution against any Windows system exposing Schannel-dependent services such as HTTPS, LDAPS, RDP with TLS, or SMB over QUIC.

Affected Products

  • Microsoft Windows (Schannel component) — refer to the Microsoft Security Update Guide for the full list of affected builds
  • Windows Server installations exposing TLS-enabled services
  • Any Windows client or server application that terminates TLS through schannel.dll

Discovery Timeline

  • 2026-10-13 - CVE-2026-105005 published to the National Vulnerability Database
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-105005

Vulnerability Analysis

Schannel is the Windows Security Support Provider (SSP) that implements SSL and TLS. It is loaded by Internet Information Services (IIS), Remote Desktop Services, LDAP over SSL, and any process that calls AcquireCredentialsHandle with the Unisp or Schannel package. A memory corruption flaw inside this component is reachable before authentication completes, which is why the attack vector is network and privileges required are none.

The vulnerability is classified under [CWE-787] Out-of-bounds Write. Successful exploitation corrupts memory in the context of the process hosting the TLS endpoint, which on server roles frequently runs with elevated privileges. The high attack complexity reflects that reliable exploitation likely depends on heap grooming, timing, or specific protocol state rather than a single malformed packet.

Microsoft has not released public technical details describing the specific message type or parsing path. See the Microsoft Security Update Guide for the authoritative advisory.

Root Cause

The root cause is an out-of-bounds write inside Schannel's handling of attacker-controlled protocol data. A size, offset, or length value is trusted without adequate validation, allowing a write beyond the bounds of an allocated buffer. This condition commonly arises in TLS handshake parsers that process variable-length structures such as extensions, certificates, or key exchange messages.

Attack Vector

The attacker initiates or responds to a TLS connection against a vulnerable Windows endpoint and sends a crafted handshake or record that triggers the out-of-bounds write. No credentials or user interaction are required. Any service that terminates TLS using Schannel represents an exposed surface, including HTTPS, LDAPS, RDP with TLS, EAP-TLS, SMTP STARTTLS on Exchange, and SMB over QUIC.

No public proof-of-concept is available. The vulnerability mechanism is described in prose only; refer to Microsoft's advisory for additional context.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-105005

Indicators of Compromise

  • Unexpected crashes or restart loops of lsass.exe, w3wp.exe, or other processes that load schannel.dll
  • Windows Error Reporting (WER) entries referencing schannel.dll with access violation exceptions
  • Anomalous TLS handshakes from untrusted sources, especially malformed ClientHello or extension payloads followed by process termination

Detection Strategies

  • Monitor Event IDs 1000 and 1001 in the Application log for crashes in modules loaded with schannel.dll
  • Inspect network telemetry for TLS handshakes with abnormally sized extensions, oversized certificate chains, or non-standard cipher suite lists
  • Correlate failed TLS connections with subsequent child process creation or memory anomalies on the host

Monitoring Recommendations

  • Enable Schannel event logging by setting the EventLogging registry value under HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL to capture handshake failures
  • Collect EDR telemetry on processes that host TLS endpoints and alert on crashes, exception codes, and unexpected module loads
  • Baseline inbound TLS traffic on exposed services and alert on sudden volume changes from new source IPs targeting LDAPS, RDP, or IIS

How to Mitigate CVE-2026-105005

Immediate Actions Required

  • Apply the Microsoft security update referenced in the Microsoft Security Update Guide to all affected Windows systems
  • Prioritize internet-facing systems that terminate TLS, including IIS web servers, Exchange, AD FS, RDP gateways, and domain controllers exposing LDAPS
  • Audit which processes load schannel.dll and confirm the patched version is in use after reboot

Patch Information

Microsoft published fixes through the Microsoft Security Update Guide on 2026-10-13. The patched schannel.dll replaces the vulnerable parsing logic. Review the advisory to identify the correct Knowledge Base article and build number for each Windows version in scope, then validate installation using wmic qfe list or Get-HotFix in PowerShell.

Workarounds

  • Restrict inbound access to TLS-enabled services using host firewalls, network ACLs, and VPN gating until patches are applied
  • Disable Schannel-dependent services that are not required, such as LDAPS or RDP on isolated subnets
  • Enforce mutual TLS or require client certificates on sensitive endpoints to reduce the pool of untrusted clients able to initiate handshakes
bash
# Verify patch installation on Windows
Get-HotFix | Sort-Object -Property InstalledOn -Descending | Select-Object -First 10

# Confirm schannel.dll version
(Get-Item C:\Windows\System32\schannel.dll).VersionInfo

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.