CVE-2026-44799
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 confidenceA heap-based buffer overflow vulnerability exists in the Remote Desktop Client that allows an unauthenticated attacker to execute arbitrary code by sending specially crafted data over a network connection to the client. The heap overflow indicates memory corruption that can be exploited to achieve code execution in the context of the client application.
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< 1.2.7214< 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.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Identify Remote Desktop Client versionOpen Command Prompt or PowerShell and run: mstsc.exe /version or check file properties of %SystemRoot%\System32\mstsc.exeAffected if Version number is below 1.2.7214 (or file version not shown, indicating very old build)
-
Check Microsoft Windows App versionOpen Settings > Apps > Installed Apps, find 'Microsoft Windows App', and view the version propertyAffected if Version is below 2.0.1193.0
-
Determine Windows OS version for built-in RDP clientRun 'winver' command or check System Properties to identify Windows version and build numberAffected if Running Windows 10 version 1607 (build < 14393.9234), 1809 (build < 17763.8880), 21h2 (build < 19044.7417), 22h2 (build < 19045.7417), Windows 11 23h2 (build < 22631.7219), or Windows 11 24h2 (build < 26100.8655)
-
Confirm Remote Desktop Client is enabledCheck if Remote Desktop is turned on in System Properties (right-click This PC > Properties > Remote Settings)Affected if Remote Desktop Client is enabled and the version/build falls below the affected thresholds above
-
Identify active RDP client processesOpen Task Manager, go to Details tab, and look for mstsc.exe running or check for Microsoft Windows App processes (WindowsApp.exe)Affected if Any of these client processes are running on unpatched versions
You are affected if you run any version of the Remote Desktop Client (mstsc.exe), Microsoft Windows App, or Windows OS with built-in RDP client that is below the specified version/build thresholds and have RDP client functionality enabled.
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 · scoped1.2.72142.0.1193.010.0.14393.9234
Apply security patches or updates released by the vendor for the Remote Desktop Client. If patches are unavailable, restrict network exposure of RDP clients and validate RDP connections originate from trusted sources only.
Install the latest Windows security updates containing the CVE-2026-44799 fix. Minimum fixed versions: Remote Desktop Client 1.2.7214, Windows App 2.0.1193.0, Windows 10 builds 10.0.14393.9234/10.0.17763.8880/10.0.19044.7417/10.0.19045.7417, Windows 11 builds 10.0.22631.7219/10.0.26100.8655
- Open Windows Settings and navigate to Windows Update
- Click Check for updates to download and install the latest security patches
- For Windows 10 1607/1809/21h2/22h2 and Windows 11 versions, ensure the update KB number includes the fixes for CVE-2026-44799 (refer to Microsoft Security Response Center for specific KB articles)
- Restart the system after updates are installed
- Verify the installed version matches or exceeds: Remote Desktop Client 1.2.7214, Windows App 2.0.1193.0, or the respective Windows build numbers (10.0.14393.9234, 10.0.17763.8880, 10.0.19044.7417, 10.0.19045.7417, 10.0.22631.7219, or 10.0.26100.8655)
- Alternatively, manually download and install the specific security update from the Microsoft Update Catalog for your Windows version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44799 — 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-44799 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