CVE-2026-47289
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 · uneditedHeap-based buffer overflow in Remote Desktop Client allows an unauthorized 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 confidenceHeap-based buffer overflow vulnerability in Microsoft's Remote Desktop Client that can be exploited by an unauthenticated remote attacker to achieve arbitrary code execution on the target system.
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< 2.0.1193.0< 10.0.14393.9234< 10.0.17763.8880< 10.0.19044.7417< 10.0.19045.7417< 10.0.22631.7219< 10.0.26100.8655< 10.0.26200.8655CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun 'winver' or 'systeminfo' from command prompt and note the full version number shownAffected if The version is below any of these thresholds: Windows 10 1607 < 10.0.14393.9234, Windows 10 1809 < 10.0.17763.8880, Windows 10 21h2 < 10.0.19044.7417, Windows 10 22h2 < 10.0.19045.7417, Windows 11 23h2 < 10.0.22631.7219, Windows 11 24h2 < 10.0.26100.8655, or Windows 11 25h2 < 10.0.26200.8655
-
Check Microsoft Windows App versionRun 'Get-AppxPackage -Name Microsoft.RemoteDesktop' in PowerShell and note the Version fieldAffected if The Version is present and less than 2.0.1193.0
-
Confirm RDP client is presentVerify that mstsc.exe exists in System32 or SysWOW64, or check that Remote Desktop Services are enabled in Services.mscAffected if The RDP client executable is present on the system
-
Identify exposure to untrusted RDP serversReview network connections or firewall rules for outbound RDP traffic (port 3389) to determine if the client can connect to external or untrusted RDP serversAffected if The system can initiate RDP connections to network locations that are not explicitly trusted
You are affected if your Windows version or Microsoft Windows App version falls below the affected thresholds AND you use the Remote Desktop Client to connect to servers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.0.1193.010.0.14393.923410.0.17763.8880
Apply the vendor security patch or update Remote Desktop Client to the latest patched version once released by Microsoft.
Windows 10 1607: 10.0.14393.9234 or later | Windows 10 1809: 10.0.17763.8880 or later | Windows 10 21h2: 10.0.19044.7417 or later | Windows 10 22h2: 10.0.19045.7417 or later | Windows 11 23h2: 10.0.22631.7219 or later | Windows 11 24h2: 10.0.26100.8655 or later | Windows 11 25h2: 10.0.26200.8655 or
- Identify the Windows version and build number by running 'winver' or 'systeminfo'
- For Windows 10/11: Open Settings > Windows Update > Check for updates, or manually download the security update from Microsoft Update Catalog matching your OS version and build
- For Windows App (Remote Desktop Client): Download and install version 2.0.1193.0 or later from the Microsoft Store or official download page
- After updating, verify the version by checking 'About' in the Remote Desktop Client or running 'winver' to confirm the build number matches or exceeds the fixed version for your OS
- Restart the Remote Desktop Client and test connectivity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47289 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47289 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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