dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24061

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Protection mechanism failure in Windows Mark of the Web (MOTW) allows an unauthorized attacker to bypass a security feature locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Windows Mark of the Web (MOTW) security feature can be bypassed locally due to a protection mechanism failure. MOTW is a Windows security feature that tags files downloaded from the internet or originating from untrusted zones, triggering warnings or restricted behaviors. This bypass allows an unauthorized local attacker to circumvent the MOTW protection, potentially enabling execution of malicious files that would normally be blocked or generate security warnings.

MitigationApply Microsoft security updates for CVE-2025-24061 when available. Until then, implement defense-in-depth controls including application whitelisting, restricting local script execution, and monitoring for suspicious file activity. Consider disabling file execution from user-accessible directories and enforcing restrictive macro settings in Office applications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows 10 1809Operating system
Affected:< 10.0.17763.7009
Windows 10 21h2Operating system
Affected:< 10.0.19044.5608
Windows 10 22h2Operating system
Affected:< 10.0.19045.5608
Windows 11 22h2Operating system
Affected:< 10.0.22621.5039
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3403> 10.0.26100.3403, < 10.0.26100.3476

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' from command prompt or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows build number
    Affected if The build number is lower than the fixed versions: < 10.0.10240.20947 (1507), < 10.0.14393.7876 (1607), < 10.0.17763.7009 (1809), < 10.0.19044.5608 (21h2), < 10.0.19045.5608 (22h2), < 10.0.22621.5039 (Win11 22h2), < 10.0.22631.5039 (Win11 23h2), < 10.0.26100.3476 (Win11 24h2, excluding 10.0.26100.34
  2. Verify MOTW is being applied to downloaded files
    Download a test file from the internet, then run 'dir /r' or use PowerShell 'Get-Item -Path "<file>" -Stream *' to check for the presence of the Zone.Identifier alternate data stream
    Affected if The downloaded file lacks the Zone.Identifier stream or the stream shows ZoneId=0 (Local Machine) instead of ZoneId=3 (Internet) or ZoneId=4 (Restricted)
  3. Check for MOTW bypass via NTFS alternate data streams
    Create a test file and attempt to copy MOTW attributes from a downloaded file using PowerShell or the 'more' command to append content, then verify if the Zone.Identifier stream is preserved or stripped
    Affected if After copying or appending content to a file, the MOTW Zone.Identifier attribute is removed or becomes invalid when it should persist

Your environment is affected if your Windows build version falls within any of the vulnerable ranges listed AND you can bypass or strip the Zone.Identifier (MOTW) from files through local file operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20947 / 10.0.14393.7876 / 10.0.17763.7009 or later
Fixed in 10.0.10240.2094710.0.14393.787610.0.17763.7009
Interim mitigation

Apply Microsoft security updates for CVE-2025-24061 when available. Until then, implement defense-in-depth controls including application whitelisting, restricting local script execution, and monitoring for suspicious file activity. Consider disabling file execution from user-accessible directories and enforcing restrictive macro settings in Office applications.

Recommended fix High confidence

Windows 10/11 with build numbers at or above the fixed versions listed (e.g., Windows 11 24h2 build 10.0.26100.3476 or later)

  1. Identify the current Windows version by running 'winver' in the Run dialog or checking System Information
  2. Determine which Windows 10 or 11 version and build number is installed
  3. For Windows 10 1507: Upgrade to build 10.0.10240.20947 or later
  4. For Windows 10 1607: Upgrade to build 10.0.14393.7876 or later
  5. For Windows 10 1809: Upgrade to build 10.0.17763.7009 or later
  6. For Windows 10 21h2: Upgrade to build 10.0.19044.5608 or later
  7. For Windows 10 22h2: Upgrade to build 10.0.19045.5608 or later
  8. For Windows 11 22h2: Upgrade to build 10.0.22621.5039 or later
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for critical systems before deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24061 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data