CVE-2025-49716
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 · uneditedUncontrolled resource consumption in Windows Netlogon allows an unauthorized attacker to deny service 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 confidenceThis is a denial-of-service vulnerability in Windows Netlogon, the RPC service used for Windows domain authentication. An unauthenticated remote attacker can send specially crafted requests to cause uncontrolled resource consumption, potentially rendering the Netlogon service unresponsive and disrupting domain authentication services.
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 dataall versions= r2all versions= r2< 10.0.14393.8246< 10.0.17763.7558< 10.0.20348.3932< 10.0.25398.1732CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the system is a Windows Server variantRun 'systeminfo' or check System Properties to confirm the operating system is Microsoft Windows Server (2008, 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, or 2022 23h2)Affected if The system is not a Windows Server in the listed product family - not affected
-
Check the installed Windows Server versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact build number (e.g., 10.0.14393 for Server 2016, 10.0.17763 for Server 2019, 10.0.20348 for Server 2022)Affected if The build number falls within the affected ranges: Server 2016 < 10.0.14393.8246, Server 2019 < 10.0.17763.7558, Server 2022 < 10.0.20348.3932, Server 2022 23h2 < 10.0.25398.1732, or Server 2008/2012 any version - AFFECTED if any of these conditions match
-
Confirm the Netlogon service is present and runningRun 'Get-Service Netlogon' in PowerShell or check Services.msc for the Netlogon (Netlogon) service statusAffected if The Netlogon service exists on the system - the vulnerability applies to this service
-
Determine if the server is functioning as a Domain ControllerRun 'nltest /dsgetdc:localhost' or check if the system holds the 'Domain Controller' server role via 'netdom query fsmo' or Server ManagerAffected if The server is a Domain Controller or runs the Netlogon service for domain authentication - the attack surface is present
A Windows Server (2008 through 2022 23h2) with a build number below the patched thresholds that runs the Netlogon service is vulnerable to this denial-of-service condition.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.824610.0.17763.755810.0.20348.3932
Apply the Microsoft security update for CVE-2025-49716 to all affected Windows domain controllers and servers running the Netlogon service. If patches are unavailable immediately, consider network segmentation or firewall rules to limit untrusted network access to Netlogon ports (TCP 135, 139, 445, and dynamic ports).
Windows Server 2016 to build 10.0.14393.8246+ | Windows Server 2019 to build 10.0.17763.7558+ | Windows Server 2022 to build 10.0.20348.3932+ | Windows Server 2022 23h2 to build 10.0.25398.1732+
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- For Windows Server 2016, upgrade to build 10.0.14393.8246 or later
- For Windows Server 2019, upgrade to build 10.0.17763.7558 or later
- For Windows Server 2022, upgrade to build 10.0.20348.3932 or later
- For Windows Server 2022 23h2, upgrade to build 10.0.25398.1732 or later
- Apply updates via Windows Update, WSUS, or download from Microsoft Update Catalog
- Verify the update was successful by checking the build version after rebooting
- For Windows Server 2008 and 2012: These versions are out of mainstream support; migrate to a supported Windows Server version (2016 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49716 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49716 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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