CVE-2022-41049
Windows Mark of the Web Security Feature Bypass Vulnerability
- CVSS
- 5.4Mediumscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 14 Nov 2022CISA deadline for US federal agencies: 9 Dec 2022
- EPSS
- 3.3%chance of exploitation in the next 30 daystop 12% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 9 Nov 2022analysed here 12 Nov 2026
Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)
Summary
Triage
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- Partly. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507 | >= 10.0.10240.0 and < 10.0.10240.19567Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.14393.0 and < 10.0.14393.5501Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.17763.0 and < 10.0.17763.3650>= 10.0.0 and < 10.0.17763.3650Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 20H2 | >= 10.0.0 and < 10.0.19042.2251Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H1 | >= 10.0.0 and < 10.0.19043.2251Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H2 | >= 10.0.19043.0 and < 10.0.19044.2251Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 22H2 | >= 10.0.19045.0 and < 10.0.19045.2251Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 21H2 | >= 10.0.0 and < 10.0.22000.1219Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H2 | >= 10.0.22621.0 and < 10.0.22621.819Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.14393.0 and < 10.0.14393.5501Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.14393.0 and < 10.0.14393.5501Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.17763.0 and < 10.0.17763.3650Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.17763.0 and < 10.0.17763.3650Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.1249Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- microsoft:windows_10_1507
- microsoft:windows_10_1607
- microsoft:windows_10_1809
- microsoft:windows_10_20h2
- microsoft:windows_10_21h1
- microsoft:windows_10_21h2
- microsoft:windows_10_22h2
- microsoft:windows_11_21h2
- microsoft:windows_11_22h2
- microsoft:windows_server_2016
- microsoft:windows_server_2019
- microsoft:windows_server_2022
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 14 Nov 2022.
- CISA due date
- 9 Dec 2022, the remediation deadline for US federal agencies
- CISA required action
- Apply updates per vendor instructions.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation active, automatable no, technical impact partialAssessed by CISA 20 Aug 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 9 Nov 2022Published
- 14 Nov 2022Added to CISA KEV (exploited in the wild)4 days later
- 9 Dec 2022CISA remediation due date (US federal agencies)25 days later
- 20 Aug 2025CISA SSVC assessment: exploitation active985 days (about 3 years) later
- 10 Aug 2026CVE record last updated355 days (about 12 months) later
- 12 Nov 2026Analysed by vulneraibility.com94 days (about 3 months) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | NoneNo data disclosure. | No data disclosure. |
| Integrity | LowLimited modification possible. | Limited modification possible. |
| Availability | LowPartial degradation possible. | Partial degradation possible. |
Common questions
Is CVE-2022-41049 being exploited?
Yes. CVE-2022-41049 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2022-41049?
CVE-2022-41049 is rated Medium with a CVSS score of 5.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-41049?
Yes. A fix has been recorded for CVE-2022-41049. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2022-41049 affect?
CVE-2022-41049 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_20h2, and 8 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Patches (1)
- msrc.microsoft.com /update-guide/vulnerability/CVE-2022-41049
Other links (1)
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-41049
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.