CVE-2023-32049VulnerabilityPublished 11 Jul 2023Updated 21 Oct 2025

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

Affects Microsoft Windows 10 Version 1809Source CVE Database V5

Exploited in the wild · KEV due 1 Aug 2023 · 4% EPSS : apply the vendor's fix or mitigations to Microsoft Windows 10 Version 1809 now.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.8High

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

KEV deadline: 1 Aug 2023 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 4.1% chance of exploitation in 30 days – higher than 90% 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:H/I:H/A:H/E:F/RL:O/RC:C

Base metrics

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
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 11 Jul 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV the same day as disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by microsoft
2023-05-0115:34Z, 71 days before disclosure
CVE published
on cve.org
2023-07-1117:02Z, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2023-07-11, the same day as disclosure
KEV remediation due
US federal deadline
2023-08-01, 21 days after disclosure

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

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 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 updates per vendor instructions or discontinue use of the product if updates are unavailable.

Affected software

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

Description

CVE-2023-32049 is a high-severity security feature bypass vulnerability affecting Microsoft Windows 10 Version 1809, specifically targeting the Windows SmartScreen feature. This vulnerability allows an attacker to bypass SmartScreen protections, potentially leading to full compromise of confidentiality, integrity, and availability without requiring privileges but needing user interaction. Although no known exploits are currently reported in the wild, the vulnerability's ease of exploitation and impact make it a significant risk. European organizations using Windows 10 Version 1809 are at risk, especially those in sectors with high reliance on legacy systems. Mitigation involves applying available patches or upgrading to supported Windows versions, disabling SmartScreen only as a last resort, and enhancing endpoint protection and user awareness. Countries with higher Windows 10 1809 usage and critical infrastructure reliance, such as Germany, France, Italy, Spain, and the UK, are most likely affected. Given the CVSS 3.1 score of 8.8, this vulnerability is classified as high severity and demands prompt attention from defenders.

Impact

For European organizations, this vulnerability poses a significant threat, particularly to those still operating Windows 10 Version 1809 in production environments. The bypass of SmartScreen reduces the effectiveness of a key security control designed to prevent malware execution and phishing attacks, potentially leading to increased successful compromises. Confidentiality could be breached through data exfiltration, integrity compromised by unauthorized code execution or system modifications, and availability impacted by ransomware or destructive malware. Sectors such as finance, healthcare, manufacturing, and government, which often rely on legacy systems, are at heightened risk. The lack of required privileges lowers the barrier for attackers, and the need for user interaction means phishing or social engineering campaigns could trigger exploitation. The absence of known exploits in the wild provides a window for mitigation, but the high CVSS score underscores the urgency. Failure to address this vulnerability could lead to significant operational disruptions and data breaches within European enterprises.

Mitigation

European organizations should prioritize upgrading from Windows 10 Version 1809 to a supported and patched Windows version to eliminate exposure. If immediate upgrade is not feasible, organizations must apply any available security updates or patches from Microsoft as soon as they are released. In the interim, consider disabling SmartScreen only if absolutely necessary and with compensating controls in place, as this reduces protection against malicious content. Enhance endpoint detection and response (EDR) capabilities to identify suspicious activities that may bypass SmartScreen. Conduct targeted user awareness training focusing on phishing and social engineering risks, emphasizing the importance of cautious interaction with unknown files or links. Network segmentation and strict application whitelisting can limit the spread and impact of potential exploits. Regularly audit systems to identify devices still running the vulnerable Windows 10 Version 1809 build and prioritize remediation. Employ multi-factor authentication and robust backup strategies to mitigate impact from potential ransomware or data integrity attacks.

Summary

CVE-2023-32049 is a vulnerability identified in Microsoft Windows 10 Version 1809 that allows an attacker to bypass the Windows SmartScreen security feature. SmartScreen is designed to protect users from phishing and malware by warning or blocking unrecognized or potentially malicious applications and files. The bypass means that malicious payloads or phishing attempts could evade these protections, increasing the risk of successful attacks. The vulnerability has a CVSS 3.1 base score of 8.8, indicating high severity, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The impact is high across confidentiality, integrity, and availability, meaning an attacker could execute arbitrary code, steal sensitive data, or disrupt system operations. No known exploits in the wild have been reported yet, but the vulnerability's nature makes it a critical concern for legacy Windows 10 systems still in operation. The affected version is specifically Windows 10 build 17763.0, which corresponds to Version 1809, a release that has reached end of support for many organizations, increasing risk exposure due to lack of updates.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2025, 23:47 UTC

Technical details

References

Community reviews

Related threats