CVE-2022-41049: Microsoft Windows Mark of the Web (MOTW) Security Feature Bypass
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-11-14.
- CVSS v3.1 (CVE record)
- 5.4
- medium
- EPSS (exploit probability, 30 days)
- 3.2%
- higher than 88.2% of all CVEs
- Added to CISA KEV
- 2022-11-14
- US federal due date 2022-12-09
- Automatable (CISA SSVC)
- no
- technical impact: partial
CVE-2022-41049 explained
CVE-2022-41049 is a security feature bypass vulnerability in Microsoft Windows Mark of the Web (MOTW). It results in a limited loss of integrity and availability of security features. CISA lists it as known to be exploited, so affected Windows systems should be updated promptly.
Impact
An attacker can bypass the Mark of the Web security feature, causing a limited loss of integrity and availability of security features. Confidentiality is not affected. The attack can be carried out over the network with low complexity and no privileges, but it requires user interaction. CISA rates it as not automatable with partial technical impact. CISA's catalog lists it as known to be exploited; ransomware use is unknown.
Who is affected
The CVE record lists Windows 10 versions 1507, 1607, 1809, 20H2, 21H1, 21H2 and 22H2, Windows 11 versions 21H2 and 22H2, Windows Server 2016 (including Server Core installation) and Windows Server 2019. Fixed builds include 10.0.10240.19567 (1507), 10.0.14393.5501 (1607, Server 2016), 10.0.17763.3650 (1809, Server 2019), 10.0.19042.2251 to 10.0.19045.2251 (20H2 to 22H2, by matching build), 10.0.22000.1219 (Windows 11 21H2) and 10.0.22621.819 (Windows 11 22H2). The page lists further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows Mark of the Web (MOTW) contains a security feature bypass vulnerability resulting in a limited loss of integrity and availability of security features.
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 150732-bit, x64AffectedFixed in
- < 10.0.10240.19567
- 10.0.10240.19567
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.2251
- 10.0.19042.2251
- Microsoft Windows 10 Version 21H132-bit, ARM64, x64AffectedFixed in
- < 10.0.19043.2251
- 10.0.19043.2251
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.2251
- 10.0.19044.2251
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.2251
- 10.0.19045.2251
- Microsoft Windows 11 version 21H2ARM64, x64AffectedFixed in
- < 10.0.22000.1219
- 10.0.22000.1219
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.819
- 10.0.22621.819
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1249
- 10.0.20348.1249
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 10 Version 21H132-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 21H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.19567
- Microsoft Windows 10 Version 1607: 10.0.14393.5501
- Microsoft Windows 10 Version 1809: 10.0.17763.3650
- Microsoft Windows 10 Version 20H2: 10.0.19042.2251
- Microsoft Windows 10 Version 21H1: 10.0.19043.2251
- Microsoft Windows 10 Version 21H2: 10.0.19044.2251
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41049
- CISA's deadline for US federal agencies: 2022-12-09 (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 patching, since CISA lists this vulnerability as known to be exploited; federal agencies had a due date of 2022-12-09.
- Verify the installed OS build on all Windows 10, Windows 11 and Windows Server 2016/2019 systems after updating.
- Remind users to be cautious when opening files from untrusted sources, since exploitation requires user interaction.
- Follow the Microsoft advisory for any additional guidance on affected products.
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-274
Questions about CVE-2022-41049
- Is CVE-2022-41049 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-11-14. Whether it is used in ransomware campaigns is listed as unknown.
- Why fix it if the severity is medium?
- Attackers are known to use it, and it requires no privileges over the network, only user interaction. CISA requires applying updates per vendor instructions.
- How do I know a system is fixed?
- Check that its OS build is at or above the fixed build for its version, for example
10.0.19045.2251for Windows 10 22H2 or10.0.17763.3650for Windows Server 2019.
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.