dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29969

HIGH · 7.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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
Time-of-check time-of-use (toctou) race condition in Windows Fundamentals allows an authorized attacker to execute code over a network.

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 · low confidence

This is a time-of-check time-of-use (TOCTOU) race condition vulnerability in a Windows core component (Windows Fundamentals). The flaw allows an authenticated attacker to exploit the window between when a security check is performed and when the check result is used, potentially allowing arbitrary code execution over a network by manipulating the system state during this race window.

MitigationApply Microsoft security updates for affected Windows versions once released; review and harden Windows network authentication configurations as an interim measure.

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.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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. Determine installed Windows version and build number
    Open Command Prompt or PowerShell and run: winver OR run 'systeminfo' and look at the OS Version / Build number field
    Affected if The build number is lower than any of these thresholds: 10.0.10240.21014 (Win10 1507), 10.0.14393.8066 (Win10 1607), 10.0.17763.7314 (Win10 1809), 10.0.19044.5854 (Win10 21h2), 10.0.19045.5854 (Win10 22h2), 10.0.22621.5335 (Win11 22h2), 10.0.22631.5335 (Win11 23h2), 10.0.26100.4061 (Win11 24h2)
  2. Identify Windows edition/release
    Run 'winver' or check System Properties to confirm whether the system is Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 22h2, 23h2, 24h2
    Affected if The edition matches any of the affected versions listed above and the build number is below the corresponding threshold
  3. Verify Windows Fundamentals component status
    This vulnerability exists in a Windows core component. No specific service or feature toggle needs to be checked - the flaw is present in the OS baseline for affected versions
    Affected if Running an unpatched Windows version within the affected build ranges

The environment is affected if the installed Windows version and build number fall below any of the specified threshold builds for the corresponding Windows release.

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.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply Microsoft security updates for affected Windows versions once released; review and harden Windows network authentication configurations as an interim measure.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21014+ | Windows 10 1607: 10.0.14393.8066+ | Windows 10 1809: 10.0.17763.7314+ | Windows 10 21h2: 10.0.19044.5854+ | Windows 10 22h2: 10.0.19045.5854+ | Windows 11 22h2: 10.0.22621.5335+ | Windows 11 23h2: 10.0.22631.5335+ | Windows 11 24h2: 10.0.26100.4061+

  1. Check current Windows build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version (10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, or 11 24h2) is currently installed
  3. For Windows 10 1507: Upgrade to build 10.0.10240.21014 or later
  4. For Windows 10 1607: Upgrade to build 10.0.14393.8066 or later
  5. For Windows 10 1809: Upgrade to build 10.0.17763.7314 or later
  6. For Windows 10 21h2: Upgrade to build 10.0.19044.5854 or later
  7. For Windows 10 22h2: Upgrade to build 10.0.19045.5854 or later
  8. For Windows 11 22h2: Upgrade to build 10.0.22621.5335 or later
Caveat Standard Windows incremental updates typically do not introduce breaking changes; however, verify application compatibility before deploying in enterprise environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing20.0 h
  • Review / QA12.0 h
80.0 hours of engineering $13,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29969 — 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-29969 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