dbcve.org
Windows Server 2022Operating system · Microsoft

CVE-2026-45648

HIGH · 8.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.20348.5256 / 10.0.26100.32995 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
Stack-based buffer overflow in Active Directory Domain Services 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 · moderate confidence

Stack-based buffer overflow vulnerability in Active Directory Domain Services enabling an authorized attacker to execute arbitrary code over the network. The flaw exists in the AD DS component handling network communications, likely in a string processing or memory copy operation on the stack.

MitigationApply vendor-supplied patches for Windows Server AD DS immediately; restrict network access to domain controllers to authorized management stations; monitor for indicators of compromise.

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 Server 2022Operating system
Affected:< 10.0.20348.5256
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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. Identify Windows Server version and build number
    Run 'winver' or 'systeminfo' from command prompt, or check the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and look at the CurrentBuild and DisplayVersion values
    Affected if The build number is below 10.0.20348.5256 for Server 2022 or below 10.0.26100.32995 for Server 2025 and the system is a domain controller
  2. Confirm the system is running Windows Server 2022 or 2025
    Examine the 'Display version' value from winver output or the ProductName from the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    Affected if The operating system is Windows Server 2022 or Windows Server 2025
  3. Verify Active Directory Domain Services role is installed
    Run 'Get-WindowsFeature -Name AD-Domain-Services' in PowerShell on the server, or check Server Manager under Add Roles and Features
    Affected if The AD-Domain-Services role is installed and the state shows 'Installed'
  4. Determine if the server is configured as a domain controller
    Run 'netdom query fsmo' or check the 'Services' snap-in for 'Active Directory Domain Services' running status, or use PowerShell: Get-Service -Name NTDS
    Affected if The server is an active domain controller with the NTDS service running
  5. Compare installed build against affected version ranges
    Note the exact build number from step 1 and compare: for Server 2022 the threshold is 20348.5256, for Server 2025 the threshold is 26100.32995
    Affected if The installed build number falls below the respective threshold for the Windows Server version in use and AD DS is active

The environment is affected if the system runs Windows Server 2022 below build 20348.5256 or Server 2025 below build 26100.32995, has the Active Directory Domain Services role installed, and is functioning as a domain controller.

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.20348.5256 / 10.0.26100.32995 or later
Fixed in 10.0.20348.525610.0.26100.32995
Interim mitigation

Apply vendor-supplied patches for Windows Server AD DS immediately; restrict network access to domain controllers to authorized management stations; monitor for indicators of compromise.

Recommended fix High confidence

Windows Server 2022: build 10.0.20348.5256 or later; Windows Server 2025: build 10.0.26100.32995 or later

  1. Identify current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows Server 2022: Upgrade to build 10.0.20348.5256 or later via Windows Update, or download and install the latest security updates from Microsoft Update Catalog
  3. For Windows Server 2025: Upgrade to build 10.0.26100.32995 or later via Windows Update, or download and install the latest security updates from Microsoft Update Catalog
  4. After upgrade, verify the new build version matches or exceeds the fixed version using 'winver' or 'systeminfo'
  5. Test critical Active Directory Domain Services functionality post-upgrade to ensure proper operation
Caveat Standard caution applies: test in non-production environment first; ensure backup of AD DS configuration before applying updates

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

Fix this in Windows Server 2022 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-2026-45648 — 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-45648 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