Skip to content
Server Security Center
KEVmedium5.4 Used in ransomware campaigns

CVE-2022-41091: Microsoft Windows Mark of the Web (MOTW) Security Feature Bypass

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

CVSS v3.1 (CVE record)
5.4
medium
EPSS (exploit probability, 30 days)
2.3%
higher than 83.3% of all CVEs
Added to CISA KEV
2022-11-08
US federal due date 2022-12-09
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2022-41091 explained

CVE-2022-41091 is a security feature bypass in Microsoft Windows Mark of the Web (MOTW). It causes a limited loss of integrity and availability of security features. CISA lists it as known exploited, with known ransomware use. That makes patching urgent despite its medium severity rating.

Impact

An attacker can bypass Mark of the Web protections over the network. No privileges are needed, but a user must interact, for example by opening attacker-supplied content. Integrity and availability impact is low, and confidentiality is not affected. CISA rates the technical impact as partial and the attack as not automatable. CISA reports active exploitation, including use in ransomware campaigns.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 20H2, 21H1, 21H2 and 22H2. It also lists Windows 11 21H2 and 22H2, Windows Server 2016 (including Server Core) and Windows Server 2019. Fixed builds include 10.0.10240.19567, 10.0.14393.5501, 10.0.17763.3650, 10.0.19042.2251, 10.0.19043.2251, 10.0.19044.2251, 10.0.19045.2251, 10.0.22000.1219 and 10.0.22621.819. Each version is fixed at its own build. Further products are listed on this page.

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, x64
    Affected
    • < 10.0.10240.19567
    Fixed in
    • 10.0.10240.19567
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.5501
    Fixed in
    • 10.0.14393.5501
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.3650
    Fixed in
    • 10.0.17763.3650
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.2251
    Fixed in
    • 10.0.19042.2251
  • Microsoft Windows 10 Version 21H132-bit, ARM64, x64
    Affected
    • < 10.0.19043.2251
    Fixed in
    • 10.0.19043.2251
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.2251
    Fixed in
    • 10.0.19044.2251
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.2251
    Fixed in
    • 10.0.19045.2251
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.1219
    Fixed in
    • 10.0.22000.1219
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.819
    Fixed in
    • 10.0.22621.819
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.5501
    Fixed in
    • 10.0.14393.5501
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.5501
    Fixed in
    • 10.0.14393.5501
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.3650
    Fixed in
    • 10.0.17763.3650
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.3650
    Fixed in
    • 10.0.17763.3650
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.1249
    Fixed in
    • 10.0.20348.1249

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
    Fixed versions for 8 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41091
  • CISA's deadline for US federal agencies: 2022-12-09 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize internet-facing workstations and users who handle email attachments and downloaded files.
  3. Verify the installed build numbers across your fleet after patching.
  4. Remind users not to open unexpected files or links from untrusted sources.
  5. Check systems for signs of compromise, given the known ransomware use.

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-863 Incorrect Authorization

Questions about CVE-2022-41091

Why patch quickly if the severity is only medium?
CISA lists CVE-2022-41091 in its Known Exploited Vulnerabilities catalog and reports known ransomware use. Active exploitation outweighs the medium base score.
What deadline did CISA set?
CISA added the vulnerability to its catalog on 2022-11-08. It set a due date of 2022-12-09 for US federal agencies to apply updates per vendor instructions.
Does exploitation require user interaction?
Yes. The CVSS data shows that user interaction is required, while no privileges are needed and the attack can come over the network.

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.