dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29810

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 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
Improper access control in Active Directory Domain Services allows an authorized attacker to elevate privileges 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 · moderate confidence

This is an improper access control vulnerability in Active Directory Domain Services (AD DS) that allows an authorized attacker to elevate privileges over a network. The vulnerability stems from insufficient access control checks within AD DS, potentially allowing a user with existing network access to escalate to higher-privileged accounts or groups.

MitigationApply the Microsoft security updates for CVE-2025-29810 to all affected Windows Server instances running AD DS. Prioritize domain controllers and conduct thorough testing in a non-production environment before deploying to production.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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. Confirm AD DS role is installed
    Run 'Get-WindowsFeature -Name AD-Domain-Services' in PowerShell, or open Server Manager and check for the Active Directory Domain Services role under AD DS
    Affected if AD DS role is not present - the vulnerability only affects systems with this role installed
  2. Determine if system is a domain controller
    Run 'Get-ADDomainController' cmdlet, or run 'systeminfo' and check for 'Domain: <domainname>' indicating domain membership, or check Server Manager for Domain Controller status
    Affected if System is not a domain controller - the vulnerability specifically exists in AD DS on domain controllers
  3. Check Windows build version
    Run 'winver' or execute 'powershell -Command "[System.Environment]::OSVersion.Version"' to obtain the exact build number, then compare against the affected version list
    Affected if Build number is lower than any of these thresholds: Windows 10 1507 < 10.0.10240.20978, Windows 10 1607 < 10.0.14393.7969, Windows 10 1809 < 10.0.17763.7136, Windows 10 21h2 < 10.0.19044.5737, Windows 10 22h2 < 10.0.19045.5737, Windows 11 22h2 < 10.0.22621.5189, Windows 11 23h2 < 10.0.22631.5189, Wi

The system is affected if it runs AD DS on a domain controller with a Windows build version below the fixed releases for CVE-2025-29810.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply the Microsoft security updates for CVE-2025-29810 to all affected Windows Server instances running AD DS. Prioritize domain controllers and conduct thorough testing in a non-production environment before deploying to production.

Recommended fix High confidence

Upgrade to the version at or above: Windows 10 1507: 10.0.10240.20978 | Windows 10 1607: 10.0.14393.7969 | Windows 10 1809: 10.0.17763.7136 | Windows 10 21h2: 10.0.19044.5737 | Windows 10 22h2: 10.0.19045.5737 | Windows 11 22h2: 10.0.22621.5189 | Windows 11 23h2: 10.0.22631.5189 | Windows 11 24h2: 1

  1. Identify the current Windows version by running 'winver' or 'systeminfo'
  2. Determine the applicable product version (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2) from the affected versions list
  3. Open Windows Update by pressing Win+R and typing 'ms-settings:windowsupdate'
  4. Click 'Check for updates' and install all available security updates
  5. Alternatively, download the specific cumulative update for your Windows version from the Microsoft Update Catalog matching the fixed version threshold
  6. After installation, restart the system to complete the update
  7. Verify the update was successful by checking Windows Update history or running 'winver' to confirm the version meets or exceeds the fixed version for your product
Caveat Standard Windows security updates typically have minimal breaking changes; test in staging environment before broad deployment 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
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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