VulnerabilityPublished 10 Oct 2023Updated 21 Oct 2025

CVE-2023-36584: Microsoft Windows 10 Version 1809 · Security Feature Bypass

Affects Microsoft Windows 10 Version 1809Source CVE Database V5

Exploited in the wild · KEV due 7 Dec 2023 · public exploit available · 3% EPSS : apply the vendor's fix or mitigations to Microsoft Windows 10 Version 1809 now.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 7 Dec 2023 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 3.2% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L/E:F/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Temporal metrics

Exploit Code Maturity: Functional
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Exploit Code Maturity: Functional: Functional exploit code is available. The code works in most situations where the vulnerability exists.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 10 Oct 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 37 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Microsoft Corporation
23 Jun 202320:11 UTC, 109 days before disclosure
CVE published
on cve.org
10 Oct 202317:07 UTC, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
16 Nov 2023, 37 days after disclosure
KEV remediation due
US federal deadline
7 Dec 2023, 58 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Affected software

Product	Affected	Fixed in
Microsoft Windows 10 Version 1809	Affected =10.0.17763.0	Fixed in–

Description

Windows Mark of the Web Security Feature Bypass Vulnerability

Impact

For European organizations, the impact of CVE-2023-36584 depends largely on the presence of Windows 10 Version 1809 systems within their IT environment. Organizations still running this legacy OS version are at risk of attackers bypassing MotW protections, which could lead to execution of malicious code or unauthorized changes to system integrity. This could result in disruption of business operations, data corruption, or system instability. Although the confidentiality impact is rated as none, the integrity and availability impacts are low but non-negligible. The requirement for user interaction means phishing or social engineering campaigns could be used to exploit this vulnerability. Sectors with high reliance on legacy Windows 10 systems, such as manufacturing, healthcare, or public administration, may face increased risk. Additionally, organizations with strict regulatory requirements around system integrity and availability (e.g., financial services, critical infrastructure) should consider this vulnerability a moderate threat. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation, especially as threat actors develop new techniques. Overall, the vulnerability could facilitate footholds or lateral movement in targeted attacks if left unmitigated.

Mitigation

European organizations should first verify if any systems are still running Windows 10 Version 1809 (build 10.0.17763.0). If so, they should prioritize upgrading to a supported and patched Windows version, as this is the most effective mitigation. In the absence of immediate upgrade options, organizations should apply any available security updates from Microsoft addressing this vulnerability. Enhance email and web filtering to block or quarantine potentially malicious attachments or links that could trigger user interaction. User awareness training should emphasize the risks of opening unknown files or links, particularly from untrusted sources. Employ endpoint detection and response (EDR) solutions to monitor for suspicious behaviors indicative of MotW bypass exploitation attempts. Network segmentation can limit the spread of any compromise originating from this vulnerability. Regularly audit and inventory legacy systems to plan for timely upgrades or decommissioning. Finally, monitor threat intelligence feeds for any emerging exploit activity related to CVE-2023-36584 to respond promptly.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Oct 2025, 20:47 UTC

Technical details

References

Community reviews

Related threats