dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29957

MEDIUM · 6.2 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 →
67/100
Remediation priority · Elevated
No privileges 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
Uncontrolled resource consumption in Windows Deployment Services allows an unauthorized attacker to deny service 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

This is a local denial of service vulnerability in Windows Deployment Services (WDS). An unauthenticated, local attacker can exploit uncontrolled resource consumption to cause the WDS service to become unavailable, disrupting deployment operations.

MitigationApply the relevant Microsoft security update for Windows Deployment Services once released. If WDS is not required in the environment, consider disabling or uninstalling the role to eliminate the attack surface.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify Windows Deployment Services is installed
    Open PowerShell and run Get-WindowsFeature -Name WDS to check if the role is installed, or run Get-Service -Name WDSMC to check if the WDS service exists
    Affected if The WDS role or service is present on the system
  2. Determine the installed Windows build version
    Run 'winver' and note the build number, or run 'systeminfo | findstr /C:"OS Version"' in Command Prompt, or query the registry with 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild'
    Affected if The build number returned is lower than any of the affected version thresholds for your Windows release
  3. Identify the Windows release version
    Run 'winver' to identify whether the system is Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if The system matches any of the affected Windows releases listed in the CVE
  4. Compare against affected version ranges
    Match your identified Windows release and build number against the affected ranges: Windows 10 1507 (below 10.0.10240.21014), 1607 (below 10.0.14393.8066), 1809 (below 10.0.17763.7314), 21h2 (below 10.0.19044.5854), 22h2 (below 10.0.19045.5854); Windows 11 22h2 (below 10.0.22621.5335), 23h2 (below 10.0.22631.5335), 24h2 (below 10.0.26100.4061)
    Affected if The installed Windows version falls below the fixed version for its release and WDS is installed

A system is affected if it runs a Windows version with WDS installed that matches any of the affected release/build combinations and the build number is below the specified threshold.

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 the relevant Microsoft security update for Windows Deployment Services once released. If WDS is not required in the environment, consider disabling or uninstalling the role to eliminate the attack surface.

Recommended fix High confidence

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

  1. Identify the current Windows version by running 'winver' or checking System Information
  2. Determine which Windows 10 or 11 version branch (1507, 1607, 1809, 21h2, 22h2, 23h2, or 24h2) is currently installed
  3. For Windows 10 1507: upgrade to version 10.0.10240.21014 or later
  4. For Windows 10 1607: upgrade to version 10.0.14393.8066 or later
  5. For Windows 10 1809: upgrade to version 10.0.17763.7314 or later
  6. For Windows 10 21h2: upgrade to version 10.0.19044.5854 or later
  7. For Windows 10 22h2: upgrade to version 10.0.19045.5854 or later
  8. For Windows 11 22h2: upgrade to version 10.0.22621.5335 or later
Caveat Standard Windows update risks apply; ensure backups and test compatibility before deploying in production environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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