dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-25177

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
94/100
Remediation priority · Urgent
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 restriction of names for files and other resources 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 · low confidence

This vulnerability in Active Directory Domain Services involves improper restriction of names for files and other resources, allowing an authorized attacker to elevate privileges over a network. The issue likely permits manipulation of object names or resource identifiers to bypass access controls and gain higher-level permissions within the domain.

MitigationApply Microsoft security updates for Active Directory Domain Services when available, and review AD ACL configurations to ensure least-privilege principles are enforced across domain objects.

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 1607Operating system
Affected:< 10.0.14393.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

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

CVSS:3.1/AV:N/AC:L/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. Verify AD DS is present
    Run 'Get-WindowsFeature -Name AD-Domain-Services' in PowerShell on domain controllers, or check systeminfo for domain membership
    Affected if System is a Domain Controller or member of an Active Directory domain
  2. Check installed Windows version
    Run 'winver' or 'systeminfo | findstr /C:"OS Version"' to obtain the exact build number
    Affected if Build number falls below any of these thresholds: 14393.8957, 17763.8511, 19044.7058, 19045.7058, 22631.6783, 26100.7979, 26200.7979, or 28000.1719 depending on Windows release
  3. Confirm domain role
    Run 'netdom query /domain:%USERDOMAIN% workstation' or check 'System Information' under 'Domain' to identify if the system participates in AD
    Affected if System is joined to an Active Directory domain where the vulnerability exists on domain controllers at affected versions
  4. Review AD object naming configuration
    Use ADSI Edit or LDP.exe to inspect naming attributes of AD objects, looking for unusual or crafted object names that may exploit the restriction flaw
    Affected if Non-standard or specially crafted object names are present in the AD database

A system is affected if it runs an affected Windows version AND serves as a Domain Controller or is joined to an Active Directory domain where object name handling can be exploited.

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.14393.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply Microsoft security updates for Active Directory Domain Services when available, and review AD ACL configurations to ensure least-privilege principles are enforced across domain objects.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.8957 | Windows 10 1809: build 10.0.17763.8511 | Windows 10 21h2: build 10.0.19044.7058 | Windows 10 22h2: build 10.0.19045.7058 | Windows 11 23h2: build 10.0.22631.6783 | Windows 11 24h2: build 10.0.26100.7979 | Windows 11 25h2: build 10.0.26200.7979 | Windows 11 26

  1. 1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. 2. Click 'Check for updates' to ensure you have the latest patches
  3. 3. Install all available updates, which will include the security fix for CVE-2026-25177
  4. 4. Restart the computer when prompted to complete the installation
  5. 5. Verify the update was installed by checking Windows Update history for the relevant KB patch
Caveat Standard Windows update with no expected breaking changes; as with any system update, test critical applications after installation

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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