Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Information Disclosure in Windows Remote Desktop Protocol (RDP)

IdentifiersCVE-2026-42908CWE-125· Out-of-bounds Read

CVE-2026-42908 is an out-of-bounds read vulnerability in the Windows Remote Desktop Protocol (RDP) stack. A remote, unauthenticated attacker can send crafted RDP traffic to a vulnerable Windows system and trigger the service to return data from adjacent memory regions. According to the provided content, successful exploitation can disclose local memory addresses, which may weaken address space layout randomization (ASLR) and expose sensitive memory contents. The issue is reachable pre-authentication over the network and requires no user interaction.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthorized disclosure of information from process memory over the network. For CVE-2026-42908, the disclosed data can include local memory addresses, which can reduce the effectiveness of ASLR and aid follow-on exploitation. The vulnerability has high confidentiality impact, with no stated integrity or availability impact, but the leaked memory information could support chaining with other vulnerabilities for more serious attacks.

Mitigation

If you can’t patch tonight, do this now.

Until patches can be applied, reduce exposure by restricting RDP access behind VPNs or bastion hosts, limiting internet exposure of RDP endpoints, enforcing strong authentication, and monitoring for unusual RDP connection patterns. The provided content also recommends avoiding connections from vulnerable Remote Desktop Client instances to untrusted or attacker-controlled Remote Desktop Servers until updates are installed.

Remediation

Patch, then assume compromise.

Apply Microsoft's June 9, 2026 security updates for all affected Windows products, including relevant cumulative updates or rollup packages for supported Windows client and server versions and affected Remote Desktop client software. Prioritize patching internet-exposed RDP systems.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows App Client For Windows Desktopapplication
Microsoft CorporationWindows Rdpoperating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2025operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.