CVE-2025-32715
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 · uneditedOut-of-bounds read in Remote Desktop Client allows an unauthorized attacker to disclose information 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 confidenceAn out-of-bounds read vulnerability exists in Microsoft's Remote Desktop Client that allows an unauthenticated, remote attacker to read sensitive information from the client's memory over a network. This type of vulnerability occurs when the software accesses memory outside the bounds of allocated buffers.
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.6278< 2.0.505.0< 10.0.10240.21034< 10.0.14393.8148< 10.0.17763.7434< 10.0.19044.5965< 10.0.19045.5965< 10.0.22621.5472CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Remote Desktop Client versionOpen the Remote Desktop Client (msrdc.exe), go to the About or Settings menu to view the version number. Alternatively, right-click the executable, select Properties, and check the Details tab for version info.Affected if The version is less than 1.2.6278
-
Check Microsoft Windows App versionOpen the Microsoft Windows App from the Start menu, click on the three-dot menu or profile icon, and look for About or version information. The version is also visible in Windows Settings under Apps > Installed Apps finding Microsoft Windows App.Affected if The version is less than 2.0.505.0
-
Check Windows 10 build versionOpen Command Prompt and run 'winver' or go to Settings > System > About to view the Windows specification. Note the OS Build number (for example, 10.0.19045.5965).Affected if Running Windows 10 1507 with build below 10.0.10240.21034, Windows 10 1607 below 10.0.14393.8148, Windows 10 1809 below 10.0.17763.7434, Windows 10 21h2 below 10.0.19044.5965, or Windows 10 22h2 below 10.0.19045.5965
-
Check Windows 11 22h2 build versionOpen Command Prompt and run 'winver' or go to Settings > System > About to view the Windows specification. Note the OS Build number (for example, 10.0.22621.5472).Affected if Running Windows 11 version 22h2 with build below 10.0.22621.5472
You are affected if the Remote Desktop Client version is below 1.2.6278, the Windows App version is below 2.0.505.0, or your Windows OS build falls within any of the vulnerable version ranges listed for Windows 10 or Windows 11 22h2.
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.62782.0.505.010.0.10240.21034
Apply Microsoft security updates for the Remote Desktop Client as they become available. Until patched, limit RDP connections to trusted servers and network paths to reduce exposure to malicious RDP servers.
Remote Desktop Client 1.2.6278+ | Windows App 2.0.505.0+ | Windows 10 1507 build 10.0.10240.21034+ | Windows 10 1607 build 10.0.14393.8148+ | Windows 10 1809 build 10.0.17763.7434+ | Windows 10 21h2 build 10.0.19044.5965+ | Windows 10 22h2 build 10.0.19045.5965+ | Windows 11 22h2 build 10.0.22621.54
- Identify the affected product from: Remote Desktop Client, Windows App, Windows 10 (1507, 1607, 1809, 21h2, 22h2), or Windows 11 22h2
- Run 'winver' to determine your current Windows version and build number
- For Windows 10/11 systems: Open Settings > Update & Security > Windows Update and install all available updates
- Alternatively, manually download the latest cumulative update for your specific Windows version from the Microsoft Update Catalog (catalog.update.microsoft.com)
- For Remote Desktop Client: Update through Microsoft Store or download the latest version from Microsoft's official Remote Desktop Client page
- For Windows App: Update through Microsoft Store to version 2.0.505.0 or later
- Verify the fix by running 'winver' and confirming the build number meets or exceeds the fixed version for your product
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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 $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32715 — 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-2025-32715 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