Skip to main content
Mallory
MediumVulnerability

CVE-2026-20824: Mark of the Web Bypass in Windows Remote Assistance

Published Jan 13, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS0.86%59th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-20824CWE-693 · Protection Mechanism Failure

CVE-2026-20824 is a security feature bypass vulnerability in Windows Remote Assistance caused by improper enforcement of downloaded-content protections. The flaw is classified as a protection mechanism failure and allows Windows Remote Assistance to incorrectly validate or process content originating from the internet, enabling bypass of Mark of the Web (MOTW) protections. In practical terms, a specially crafted file can be presented to a user in a way that avoids the normal MOTW-based safeguards that Windows and dependent security controls apply to internet-sourced content. Exploitation requires local execution and user interaction, typically by convincing a target to open the crafted file. The vulnerability affects multiple supported Windows client and server platforms and was addressed by Microsoft in January 2026 security updates.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows an attacker to bypass MOTW-based security protections on affected Windows systems. This can suppress or weaken security prompts, restricted execution behaviors, and downstream inspection or enforcement performed by controls that rely on MOTW metadata. The documented CVSS assessment indicates high confidentiality impact, with no direct integrity or availability impact. In attack chains, the vulnerability can improve the success of socially engineered initial access by reducing friction and visibility around execution of internet-delivered content.

Mitigation

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

If immediate patching is not possible, reduce exposure by disabling Windows Remote Assistance where it is not operationally required and restricting which users can initiate or accept Remote Assistance sessions through policy. Strengthen controls around externally sourced files by enforcing email and web filtering, blocking high-risk attachment types, and using endpoint protections such as SmartScreen, Attack Surface Reduction rules, Protected View, and application control mechanisms including WDAC or AppLocker. Monitor for suspicious file execution patterns and abnormal process behavior associated with user-opened downloaded content.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates released on 2026-01-13 for affected Windows versions. Patch deployment should prioritize user-facing endpoints and other systems where users may open externally sourced files. Ensure all supported affected Windows client and server configurations receive the corresponding cumulative or security updates that remediate Windows Remote Assistance handling of downloaded content protections.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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 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 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2026-20824 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-20824 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-20824?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-20824.
Is there a patch for CVE-2026-20824?
Apply the Microsoft security updates released on 2026-01-13 for affected Windows versions. Patch deployment should prioritize user-facing endpoints and other systems where users may open externally sourced files.
What products are affected by CVE-2026-20824?
Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 10 more.
How severe is CVE-2026-20824?
CVE-2026-20824 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.86% (59th percentile) as of Sep 25, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.