dbcve.org
Windows AppApplication · Microsoft

CVE-2026-42908

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 2.0.1193.0 / 10.0.14393.9234 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Out-of-bounds read in Windows RDP 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 · high confidence

An out-of-bounds read vulnerability exists in Windows Remote Desktop Protocol (RDP) that allows an unauthenticated, remote attacker to read sensitive memory contents beyond intended buffer boundaries, leading to information disclosure. The vulnerability is exploitable over a network without user interaction.

MitigationApply the relevant Microsoft security update for Windows RDP to remediate this vulnerability. If immediate patching is not feasible, restrict RDP access via network-level authentication (NLA) or firewall rules to limit exposure to trusted networks only.

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 AppApplication
Affected:< 2.0.1193.0
Windows 10 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify RDP is enabled on the system
    Open Control Panel > System and Security > System, then click Remote settings. Alternatively, run 'Get-ItemProperty -Path 'HK:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' in PowerShell. A value of 0 means RDP is enabled.
    Affected if RDP is enabled (fDenyTSConnections = 0). The vulnerability only affects systems with RDP exposed.
  2. Determine Windows version and build
    Run 'winver' from Run dialog, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or run '[System.Environment]::OSVersion.Version' in PowerShell.
    Affected if The version is lower than any of these: Windows 10 1607 build 14393.9234, Windows 10 1809 build 17763.8880, Windows 10 21h2 build 19044.7417, Windows 10 22h2 build 19045.7417, Windows 11 23h2 build 22631.7219, Windows 11 24h2 build 26100.8655, Windows 11 25h2 build 26200.8655.
  3. Check Windows App version if applicable
    If using the Microsoft Windows App (remote desktop client), open Microsoft Store > Library > Updates, or right-click the app in Start menu and select App settings to view the version. Alternatively, run 'Get-AppxPackage -Name 'Microsoft.WindowsApp' | Select-Object Version' in PowerShell.
    Affected if The Windows App version is lower than 2.0.1193.0 and the app is used to connect to vulnerable RDP targets.

A system is affected if RDP is enabled and the Windows version or Windows App version falls below the affected version thresholds listed above.

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 2.0.1193.0 / 10.0.14393.9234 / 10.0.17763.8880 or later
Fixed in 2.0.1193.010.0.14393.923410.0.17763.8880
Interim mitigation

Apply the relevant Microsoft security update for Windows RDP to remediate this vulnerability. If immediate patching is not feasible, restrict RDP access via network-level authentication (NLA) or firewall rules to limit exposure to trusted networks only.

Recommended fix High confidence

Apply the appropriate Windows security update; fixed builds are: 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+), Windows 11 25h2 (10

  1. Open Settings > Update & Security > Windows Update on the affected Windows system
  2. Click 'Check for updates' to download and install the latest security updates from Microsoft
  3. Alternatively, visit the Microsoft Update Catalog (catalog.update.microsoft.com) and search for the CVE-2026-42908 security update specific to your Windows version
  4. After installation, restart the system to ensure the security patch is fully applied
  5. Verify the installed security update by checking Windows Update history or running 'winver' to confirm the OS build number matches or exceeds the fixed version for your Windows release

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

Fix this in Windows App Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

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