dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-60703

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 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
Untrusted pointer dereference in Windows Remote Desktop 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

A memory safety vulnerability exists in Windows Remote Desktop where an untrusted pointer is dereferenced, allowing a locally authenticated attacker to elevate privileges to SYSTEM level by exploiting the pointer handling logic in the Remote Desktop service.

MitigationApply the Microsoft security update for CVE-2025-60703 via Windows Update or enterprise patch management systems to address the untrusted pointer dereference in Remote Desktop.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2008Operating system
Affected:all versions= r2

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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows version and build number
    Affected if The installed version falls within any of these ranges: Windows 10 1607 < 10.0.14393.8594, Windows 10 1809 < 10.0.17763.8027, Windows 10 21h2 < 10.0.19044.6575, Windows 10 22h2 < 10.0.19045.6575, Windows 11 23h2 < 10.0.22631.6199, Windows 11 24h2 < 10.0.26100.7092, Windows 11 25h2 < 10.0.26200.7092,
  2. Check if Remote Desktop service is present
    Open Services console (services.msc) or run 'sc query TermService' in Command Prompt to check if the Remote Desktop Services service (TermService) exists on the system
    Affected if The TermService service exists on the system (the vulnerability is in the Remote Desktop code path regardless of whether RDP is enabled for remote connections)
  3. Verify installed security updates
    Open Control Panel > Programs > Programs and Features > View installed updates, or run 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to list recent security patches
    Affected if No Microsoft security update for CVE-2025-60703 is listed among installed updates

A system is affected if it runs any Windows version listed in the affected ranges AND has the Remote Desktop service component present, and the CVE-2025-60703 security update has not been installed.

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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply the Microsoft security update for CVE-2025-60703 via Windows Update or enterprise patch management systems to address the untrusted pointer dereference in Remote Desktop.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8594 or later | Windows 10 1809: 10.0.17763.8027 or later | Windows 10 21h2: 10.0.19044.6575 or later | Windows 10 22h2: 10.0.19045.6575 or later | Windows 11 23h2: 10.0.22631.6199 or later | Windows 11 24h2: 10.0.26100.7092 or later | Windows 11 25h2: 10.0.26200.7092 or

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually install the security update from Microsoft Catalog for your specific Windows version: KB5055528 for Windows 10 1607, KB5055518 for Windows 10 1809, KB5055523 for Windows 10 21h2/22h2, KB5055527 for Windows 11 23h2/24h2/25h2
  4. For Windows Server 2008/R2, this is End of Life - migrate to a supported Windows Server version or apply the last available security updates if still under Extended Support
  5. Restart the system after applying updates
  6. Verify the installed security update by running 'winver' or checking installed updates
Caveat Windows Server 2008/R2 is end-of-life; no further security updates available - migration required

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60703 — 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-60703 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