CVE-2025-24061: Windows Mark of the Web Security Feature Bypass Vulnerability
First published: Tue Mar 11 2025(Updated: )
<p>Protection mechanism failure in Windows Mark of the Web (MOTW) allows an unauthorized attacker to bypass a security feature locally.</p>
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Windows 11 | =23H2 | |
| Windows 11 | =24H2 | |
| Microsoft Windows Server 2025 | ||
| Microsoft Windows Server 2025 | ||
| Microsoft Windows Server 2019 | ||
| Windows 11 | =23H2 | |
| Microsoft Windows Server 2019 | ||
| Windows 11 | =22H2 | |
| Windows 11 | =22H2 | |
| Windows 11 | =24H2 | |
| Microsoft Windows Server 2022 23H2 | ||
| Microsoft Windows Server 2016 | ||
| Microsoft Windows Server 2016 | ||
| Microsoft Windows Server 2022 | ||
| Microsoft Windows Server 2022 | ||
| Windows 10 | =1809 | |
| Windows 10 | =1809 | |
| Windows 10 | =22H2 | |
| Windows 10 | =22H2 | |
| Windows 10 | =22H2 | |
| Windows 10 | =1607 | |
| Windows 10 | =1607 | |
| Windows 10 | =21H2 | |
| Windows 10 | =21H2 | |
| Windows 10 | =21H2 | |
| Windows 10 | ||
| Windows 10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability CVE-2025-24061?
CVE-2025-24061 is a protection mechanism failure in Windows Mark of the Web that allows unauthorized attackers to bypass security features locally.
What products are affected by CVE-2025-24061?
CVE-2025-24061 affects various versions of Windows 10 and Windows 11 including specific releases like 23H2 and 24H2.
How do I fix the vulnerability CVE-2025-24061?
To fix CVE-2025-24061, users should ensure they install the latest security patches provided by Microsoft.
What is the impact of the CVE-2025-24061 vulnerability?
The impact of CVE-2025-24061 may allow attackers to gain unauthorized access and perform actions that compromise system security.
Is there a workaround for CVE-2025-24061?
Currently, there are no known workaround measures besides applying the appropriate security updates to mitigate CVE-2025-24061.
- collector/msrc-cve
- source/Microsoft
- agent/title
- agent/type
- agent/first-publish-date
- agent/software-canonical-lookup
- collector/msrc
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/weakness
- agent/description
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/bleeping-computer
- source/BleepingComputer
- alias/CVE-2025-24061
- alias/CVE-2025-24071
- alias/CVE-2025-26633
- agent/news-ai
- zeroday/true
- agent/references
- agent/source
- agent/tags
- agent/event
- agent/trending
- vendor/microsoft
- canonical/windows 11
- version/windows 11/23h2
- version/windows 11/24h2
- canonical/microsoft windows server 2025
- canonical/microsoft windows server 2019
- version/windows 11/22h2
- canonical/microsoft windows server 2022 23h2
- canonical/microsoft windows server 2016
- canonical/microsoft windows server 2022
- canonical/windows 10
- version/windows 10/1809
- version/windows 10/22h2
- version/windows 10/1607
- version/windows 10/21h2