Skip to content
major vulnerability· requires attention

OpenSSH is widely deployed for remote access; a network-facing RCE in the Windows build risks broad system compromise and operational disruption.

Infrastructure

CVE-2026-83923

8.8
High
EPSS 0.92%Patch availableOct 15, 2026

Relative path traversal in OpenSSH for Windows enables remote code execution.

common questions

Is CVE-2026-83923 being exploited?

Not confirmed. CVE-2026-83923 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.92% probability of exploitation in the next 30 days.

How severe is CVE-2026-83923?

CVE-2026-83923 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-83923?

Yes. A fix has been recorded for CVE-2026-83923. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-83923 affect?

CVE-2026-83923 affects OpenSSH for Windows, Windows systems running OpenSSH (sshd), Windows Server and client builds with bundled OpenSSH. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-83923?

Apply vendor updates when available; restrict/monitor SSH exposure and rotate keys.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenSSH for WindowsWindows systems running OpenSSH (sshd)Windows Server and client builds with bundled OpenSSH
impact

Remote code execution via relative path traversal in OpenSSH for Windows; attacker can execute arbitrary code via the sshd service, risking full system compromise.

action required

Immediate action required

affected versions
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.9376
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.7807
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19044.7807
Microsoft Windows 11 version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.7652
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.7652
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.9711
Microsoft Windows 11 Version 25H2
  • affected>= 10.0.26200.0 and < 10.0.26200.9711
Microsoft Windows 11 version 26H1
  • affected>= 10.0.28000.0 and < 10.0.28000.3231
Microsoft Windows 11 Version 26H2
  • affected>= 10.0.26300.0 and < 10.0.26300.9711
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.9376
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.9376
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.5761
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33650
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33650

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free