Skip to content
Server Security Center
KEVhigh8.8

CVE-2023-32049: Microsoft Windows Defender SmartScreen Security Feature Bypass

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2023-07-11.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
4.2%
higher than 91.1% of all CVEs
Added to CISA KEV
2023-07-11
US federal due date 2023-08-01
Automatable (CISA SSVC)
no
technical impact: total

CVE-2023-32049 explained

CVE-2023-32049 is a security feature bypass vulnerability in Microsoft Windows Defender SmartScreen. It allows an attacker to bypass the Open File - Security Warning prompt. It affects several Windows 10, Windows 11 and Windows Server releases, and CISA lists it as known to be exploited by attackers.

Impact

An attacker can cause a file to open without the Open File - Security Warning prompt that would normally alert the user. The attack works over the network, needs no privileges and has low complexity, but requires user interaction. CISA rates the technical impact as total but not automatable. Confidentiality, integrity and availability impacts are all rated high. Attackers are known to use this vulnerability; ransomware use is unknown.

Who is affected

The CVE record lists Windows 10 Version 1607, 1809, 21H2 and 22H2, Windows 11 version 21H2 and 22H2, Windows Server 2016, 2019 and 2022, including Server Core installations. Fixed builds: 10.0.14393.6085 (1607, Server 2016), 10.0.17763.4645 (1809, Server 2019), 10.0.19044.3208 (10 21H2), 10.0.19045.3208 (10 22H2), 10.0.22000.2176 (11 21H2), 10.0.22621.1992 (11 22H2) and 10.0.20348.1850 (Server 2022). Earlier builds are affected.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Defender SmartScreen contains a security feature bypass vulnerability that allows an attacker to bypass the Open File - Security Warning prompt.

CISA required action: Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.4645
    Fixed in
    • 10.0.17763.4645
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.4645
    Fixed in
    • 10.0.17763.4645
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.4645
    Fixed in
    • 10.0.17763.4645
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.1850
    Fixed in
    • 10.0.20348.1850
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.2176
    Fixed in
    • 10.0.22000.2176
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.3208
    Fixed in
    • 10.0.19044.3208
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.1992
    Fixed in
    • 10.0.22621.1992
  • Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit
    Affected
    • < 10.0.19045.3208
    Fixed in
    • 10.0.19045.3208
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.6085
    Fixed in
    • 10.0.14393.6085
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.6085
    Fixed in
    • 10.0.14393.6085
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.6085
    Fixed in
    • 10.0.14393.6085

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.4645
    • Microsoft Windows Server 2019: 10.0.17763.4645
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.4645
    • Microsoft Windows Server 2022: 10.0.20348.1850
    • Microsoft Windows 11 version 21H2: 10.0.22000.2176
    • Microsoft Windows 10 Version 21H2: 10.0.19044.3208
    Fixed versions for 5 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2023-32049
  • CISA's deadline for US federal agencies: 2023-08-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security updates so each system reaches at least the fixed build listed for its Windows release.
  2. Prioritize patching because CISA lists this vulnerability as known exploited; the US federal due date was 2023-08-01.
  3. Verify the installed build number on all endpoints and servers after updating.
  4. Follow the Microsoft advisory and CISA's required action: apply updates or discontinue use if updates are unavailable.
  5. Remind users to be cautious with downloaded files and links, since exploitation requires user interaction.
  6. Check systems for signs of compromise, especially those patched late.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Questions about CVE-2023-32049

Is CVE-2023-32049 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-07-11. Whether it has been used in ransomware campaigns is unknown.
Does an attacker need an account on the system?
No privileges are required, and the attack works over the network. However, a user must interact, for example by opening a file, for the bypass to occur.
Which update fixes the issue?
The fix is included in the builds listed in the CVE record, such as 10.0.22621.1992 for Windows 11 version 22H2 and 10.0.20348.1850 for Windows Server 2022. Check the Microsoft advisory for your release.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.