dbcve.org
Remote Desktop ClientApplication · Microsoft

CVE-2025-27487

HIGH · 8.0 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 1.2.6081 / 2.0.379.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Heap-based buffer overflow in Remote Desktop Client allows an authorized attacker to execute code over a network.

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

Heap-based buffer overflow vulnerability in Remote Desktop Client that allows an authorized attacker to execute arbitrary code over a network. The vulnerability stems from improper bounds checking when handling data within the RDP client, leading to heap memory corruption that can be exploited for code execution.

MitigationApply vendor patches when released; restrict network access to trusted users and networks as this requires authorized access; consider network-level filtering for RDP connections until patch is available.

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
Remote Desktop ClientApplication
Affected:< 1.2.6081
Windows AppApplication
Affected:< 2.0.379.0
Windows 10 1507Operating system
Affected:< 10.0.10240.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
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

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Check Microsoft Remote Desktop Client version
    Run 'msrdc.exe /version' in Command Prompt or PowerShell, or right-click msrdc.exe in %ProgramFiles%\Remote Desktop and view Properties > Details > File Version
    Affected if Version is present and less than 1.2.6081
  2. Check Microsoft Windows App version
    Run 'Get-AppxPackage *Microsoft.WindowsApp* | Select-Object Name, Version' in PowerShell
    Affected if Version is present and less than 2.0.379.0
  3. Check Windows 10 version number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' or 'Get-ComputerInfo | Select-Object OsVersion' in PowerShell
    Affected if Windows 10 version is 1507 and build < 10.0.10240.20978, or version 1607 and build < 10.0.14393.7969, or version 1809 and build < 10.0.17763.7136, or version 21h2 and build < 10.0.19044.5737, or version 22h2 and build < 10.0.19045.5737
  4. Check Windows 11 version number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' or 'Get-ComputerInfo | Select-Object OsVersion' in PowerShell
    Affected if Windows 11 version is 22h2 and build < 10.0.22621.5189

A system is affected if the installed Remote Desktop Client is below 1.2.6081, Windows App is below 2.0.379.0, or the Windows OS build number falls below the threshold for the detected 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 1.2.6081 / 2.0.379.0 / 10.0.10240.20978 or later
Fixed in 1.2.60812.0.379.010.0.10240.20978
Interim mitigation

Apply vendor patches when released; restrict network access to trusted users and networks as this requires authorized access; consider network-level filtering for RDP connections until patch is available.

Recommended fix High confidence

Remote Desktop Client 1.2.6081+ | Windows App 2.0.379.0+ | Windows 10 1507 build 10.0.10240.20978+ | Windows 10 1607 build 10.0.14393.7969+ | Windows 10 1809 build 10.0.17763.7136+ | Windows 10 21h2 build 10.0.19044.5737+ | Windows 10 22h2 build 10.0.19045.5737+ | Windows 11 22h2 build 10.0.22621.51

  1. Ensure Windows Update is enabled and configured to automatically receive security updates
  2. Run Windows Update to install the latest cumulative security update for your Windows version
  3. For Remote Desktop Client specifically, update to version 1.2.6081 or later via Microsoft Store or Windows Update
  4. For Windows App, update to version 2.0.379.0 or later
  5. Verify the update was successfully installed by checking Windows Update history
  6. Restart the system if prompted to complete the installation
Caveat Standard Windows Update apply; enterprise deployments should test in staging environment before broad rollout

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

Fix this in Remote Desktop Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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