CVE-2022-44698: Microsoft Defender SmartScreen Security Feature Bypass
Microsoft Defender · listed in the CISA catalog of actively exploited vulnerabilities since 2022-12-13.
- CVSS v3.1 (CVE record)
- 5.4
- medium
- EPSS (exploit probability, 30 days)
- 75%
- higher than 99.5% of all CVEs
- Added to CISA KEV
- 2022-12-13
- US federal due date 2023-01-03
- Automatable (CISA SSVC)
- no
- technical impact: partial
CVE-2022-44698 explained
CVE-2022-44698 is a security feature bypass vulnerability in Microsoft Defender SmartScreen on Windows. A specially crafted malicious file can evade Mark of the Web (MOTW) defenses, which normally warn users about files from untrusted sources. CISA lists it as known exploited, including in ransomware campaigns, so patching should be a priority despite the medium severity rating.
Impact
An attacker can deliver a crafted file over the network that bypasses MOTW protections, removing a warning layer before a user opens it. No privileges are needed, but user interaction is required. The direct impact is limited to low integrity and availability effects, and CISA rates the technical impact as partial and not automatable. Attackers are known to exploit it, including for ransomware.
Who is affected
The CVE record lists Windows 10 Version 1607, 1809, 20H2, 21H1, 21H2 and 22H2, Windows 11 version 21H2, and Windows Server 2016, 2019 and 2022. Fixed builds: 10.0.14393.5582 (1607, Server 2016), 10.0.17763.3770 (1809, Server 2019), 10.0.19042.2364 (20H2), 10.0.19043.2364 (21H1), 10.0.19044.2364 (21H2), 10.0.19045.2364 (22H2), 10.0.22000.1335 (Windows 11 21H2) and 10.0.20348.1366 (Server 2022). Earlier builds are affected.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Defender SmartScreen contains a security feature bypass vulnerability that could allow an attacker to evade Mark of the Web (MOTW) defenses via a specially crafted malicious file.
CISA required action: Apply updates per vendor instructions.
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, ARM64AffectedFixed in
- < 10.0.17763.3770
- 10.0.17763.3770
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3770
- 10.0.17763.3770
- Microsoft Windows 10 Version 21H1x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19043.2364
- 10.0.19043.2364
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1366
- 10.0.20348.1366
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.2364
- 10.0.19042.2364
- Microsoft Windows 11 version 21H2x64, ARM64AffectedFixed in
- < 10.0.22000.1335
- 10.0.22000.1335
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.2364
- 10.0.19044.2364
- Microsoft Windows 10 Version 22H2x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19045.2364
- 10.0.19045.2364
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5582
- 10.0.14393.5582
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5582
- 10.0.14393.5582
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 11 version 21H2x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.3770
- Microsoft Windows Server 2019: 10.0.17763.3770
- Microsoft Windows 10 Version 21H1: 10.0.19043.2364
- Microsoft Windows Server 2022: 10.0.20348.1366
- Microsoft Windows 10 Version 20H2: 10.0.19042.2364
- Microsoft Windows 11 version 21H2: 10.0.22000.1335
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-44698
- CISA's deadline for US federal agencies: 2023-01-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
- Prioritize systems where users open email attachments or downloaded files, given known ransomware use.
- Verify build numbers across endpoints and servers to confirm the update was applied.
- Remind users to be cautious with files from untrusted sources, since exploitation requires user interaction.
- Check for signs of compromise on systems that remained unpatched, following the vendor advisory.
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
- Partial – limited control or information
Weakness: CWE-755
Questions about CVE-2022-44698
- Is CVE-2022-44698 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-12-13 and notes known use in ransomware campaigns. US federal agencies had a due date of 2023-01-03.
- Why patch quickly if the severity is only medium?
- The flaw lets malicious files bypass Mark of the Web warnings, removing a defense against untrusted files. Active exploitation, including by ransomware, makes it more urgent than the score alone suggests.
- What action does CISA require?
- CISA's required action is to apply updates per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.