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-83923 Overview
CVE-2026-83923 is a relative path traversal vulnerability [CWE-23] in OpenSSH for Windows. An unauthenticated attacker can exploit the flaw over a network to execute arbitrary code on the target host. Exploitation requires user interaction, which typically means the victim must initiate or accept an SSH operation such as a file transfer. Microsoft published the advisory in its Security Update Guide and tracks the issue under the same identifier.
Critical Impact
Successful exploitation grants remote code execution on Windows systems running OpenSSH, with full confidentiality, integrity, and availability impact.
Affected Products
- OpenSSH for Windows (Microsoft distribution)
- Windows systems with the OpenSSH feature enabled
- Refer to the Microsoft Security Update Guide for the complete list of affected builds
Discovery Timeline
- 2026-10-13 - CVE-2026-83923 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-83923
Vulnerability Analysis
The vulnerability stems from improper sanitization of relative path references within OpenSSH for Windows. An attacker crafts input containing ..\ or similar traversal sequences that escape the intended working directory. When OpenSSH processes the malformed path, it writes or executes files outside the expected scope.
Because OpenSSH runs with elevated privileges on Windows, writing to attacker-chosen locations enables code execution. Common targets include startup folders, service binaries, and DLL search paths. The flaw aligns with [CWE-23: Relative Path Traversal], where filename validation fails to normalize directory separators and parent references.
Exploitation does not require prior authentication but does require user interaction. The most plausible scenarios involve a victim connecting to a malicious SSH server or accepting a prepared file transfer. Attackers can chain this access with lateral movement across Windows environments where OpenSSH is widely deployed for remote administration.
Root Cause
The root cause is insufficient validation of file paths supplied through SSH protocol operations. OpenSSH for Windows accepts user-controllable path components without canonicalizing them against an allowed base directory. The Windows path parser treats both forward and backward slashes as separators, expanding the traversal surface compared to POSIX builds.
Attack Vector
The attack vector is network-based with low complexity. An attacker hosts a malicious SSH endpoint or injects crafted responses into an SSH session the victim initiates. When the client processes server-supplied filenames during operations such as SCP or SFTP, the traversal payload redirects the write to a sensitive directory. Placing a payload in a Windows startup or service path yields code execution at the next trigger.
No verified proof-of-concept code is public. See the Microsoft Security Update Guide for authoritative technical details.
Detection Methods for CVE-2026-83923
Indicators of Compromise
- SSH session logs containing filenames with ..\, ../, or encoded traversal sequences (%2e%2e)
- Unexpected file writes by sshd.exe or ssh.exe outside user profile directories
- New or modified files in Windows startup, System32, or service binary paths following SSH activity
- Outbound SSH connections to untrusted hosts from administrator workstations
Detection Strategies
- Enable OpenSSH logging in sshd_config with LogLevel VERBOSE and forward events to a centralized log platform
- Alert on process creation where sshd.exe or ssh.exe spawns cmd.exe, powershell.exe, or writes to persistence locations
- Correlate SCP/SFTP transfers with file-system modifications outside expected upload directories
Monitoring Recommendations
- Monitor Windows Event IDs 4663 and 4688 for file-write and process-creation activity tied to OpenSSH binaries
- Track changes to autorun keys, scheduled tasks, and service executables after SSH sessions
- Review network telemetry for SSH connections to new or low-reputation destinations
How to Mitigate CVE-2026-83923
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft Security Update Guide across all Windows hosts running OpenSSH
- Inventory systems with the OpenSSH client or server feature enabled and prioritize patching internet-facing hosts
- Restrict outbound SSH from user workstations to known administrative targets only
Patch Information
Microsoft has issued updates addressing CVE-2026-83923 through standard Windows Update channels. Administrators should consult the Microsoft Security Update Guide for KB numbers, affected builds, and installation guidance.
Workarounds
- Disable the OpenSSH Server and Client optional features on systems that do not require them
- Block inbound and outbound TCP port 22 at perimeter and host firewalls where SSH is not operationally needed
- Require users to connect only to known, trusted SSH servers via jump hosts or allowlists
# Disable OpenSSH features on Windows where not required
Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*'
Remove-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
Remove-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
# Block SSH at the host firewall if the service must remain installed
New-NetFirewallRule -DisplayName 'Block-SSH-Inbound' -Direction Inbound -Protocol TCP -LocalPort 22 -Action Block
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

