dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-27731

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.17763.7136 / 10.0.19044.5737 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in OpenSSH for Windows allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability in OpenSSH for Windows stems from improper input validation that allows a local authorized attacker to escalate privileges to higher permission levels. The issue likely involves insufficient sanitization of user input processed by the SSH service running on Windows, potentially enabling manipulation of execution flow or access controls.

MitigationApply vendor-provided patches for OpenSSH for Windows once available, and restrict local access to trusted personnel only while the vulnerability remains unpatched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775
Windows Server 2019Operating system
Affected:< 10.0.17763.7136
Windows Server 2022Operating system
Affected:< 10.0.20348.3453

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm OpenSSH for Windows is installed
    Open PowerShell or Command Prompt and run: Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*' to list installed OpenSSH capabilities, or check if ssh.exe exists at C:\Windows\System32\ssh.exe
    Affected if OpenSSH is installed on the system
  2. Identify the installed OpenSSH version
    Run: ssh -V (note the capital V) in Command Prompt or PowerShell to display the OpenSSH version string, or check the file version of C:\Windows\System32\ssh.exe via Properties > Details
    Affected if The version displayed is lower than the fixed builds for your Windows version
  3. Determine the Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows 10/11 or Windows Server version and build number
    Affected if The Windows build falls within an affected version range and OpenSSH is installed
  4. Compare against affected version ranges
    Cross-reference your OpenSSH version against: 10.0.17763.7136 (Win 10 1809/Server 2019), 10.0.19044.5737 (Win 10 21h2), 10.0.19045.5737 (Win 10 22h2), 10.0.22621.5189 (Win 11 22h2), 10.0.22631.5189 (Win 11 23h2), 10.0.26100.3775 (Win 11 24h2), 10.0.20348.3453 (Server 2022)
    Affected if Your OpenSSH version is less than the fixed build number for your Windows version

You are affected if OpenSSH for Windows is installed and its version is below the patched build number corresponding to your Windows version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.17763.7136 / 10.0.19044.5737 / 10.0.19045.5737 or later
Fixed in 10.0.17763.713610.0.19044.573710.0.19045.5737
Interim mitigation

Apply vendor-provided patches for OpenSSH for Windows once available, and restrict local access to trusted personnel only while the vulnerability remains unpatched.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.7136 or later | Windows 10 21h2: 10.0.19044.5737 or later | Windows 10 22h2: 10.0.19045.5737 or later | Windows 11 22h2: 10.0.22621.5189 or later | Windows 11 23h2: 10.0.22631.5189 or later | Windows 11 24h2: 10.0.26100.3775 or later | Windows Server 2019: 10.0.17763.7136

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Check OpenSSH version by running 'ssh -V' in Command Prompt
  3. Apply the appropriate Windows cumulative update for your version that includes build 10.0.17763.7136, 10.0.19044.5737, 10.0.19045.5737, 10.0.22621.5189, 10.0.22631.5189, 10.0.26100.3775, or 10.0.20348.3453 depending on your Windows edition
  4. Verify the update installed successfully by checking Windows Update history or running 'winver' again to confirm the build number matches or exceeds the fixed version for your product
  5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update risks - ensure backups and test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27731 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data