dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2025-32725

HIGH · 7.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.14393.8148 / 10.0.17763.7434 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Protection mechanism failure in Windows DHCP Server 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 confidence

A protection mechanism failure in Windows DHCP Server allows an unauthenticated remote attacker to cause a denial of service, potentially disrupting IP address assignment across the network.

MitigationApply the latest Windows security updates to affected DHCP Server systems and monitor for anomalous DHCP traffic patterns.

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 2016Operating system
Affected:< 10.0.14393.8148
Windows Server 2019Operating system
Affected:< 10.0.17763.7434
Windows Server 2022Operating system
Affected:< 10.0.20348.3745
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1665
Windows Server 2025Operating system
Affected:< 10.0.26100.4270

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows Server version
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsVersion, OsVersion, OsBuildNumber' in PowerShell to obtain the build number
    Affected if The build number is less than one of these thresholds: 14393.8148 (Server 2016), 17763.7434 (Server 2019), 20348.3745 (Server 2022), 25398.1665 (Server 2022 23h2), or 26100.4270 (Server 2025)
  2. Verify DHCP Server role is installed
    Run 'Get-WindowsFeature -Name DHCP' in PowerShell (Server 2016/2019) or 'Get-WindowsOptionalFeature -Online -FeatureName DHCP' in PowerShell (Server 2022+)
    Affected if The DHCP Server role shows as Installed or the feature state is Enabled
  3. Confirm DHCP Server service is running
    Run 'Get-Service -Name DHCPServer' in PowerShell and check the Status property
    Affected if The service exists and shows a status of Running (vulnerable attack surface is active)
  4. Cross-reference build number with affected version list
    Compare your identified build number manually against the version thresholds listed in the CVE affected products
    Affected if Your installed Windows Server version falls below any of the specified build numbers for your Server version

You are affected if your Windows Server version is below the threshold for your specific Server release AND the DHCP Server role is installed and running.

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.8148 / 10.0.17763.7434 / 10.0.20348.3745 or later
Fixed in 10.0.14393.814810.0.17763.743410.0.20348.3745
Interim mitigation

Apply the latest Windows security updates to affected DHCP Server systems and monitor for anomalous DHCP traffic patterns.

Recommended fix High confidence

Upgrade to Windows Server build 10.0.14393.8148 or higher (Server 2016); 10.0.17763.7434 or higher (Server 2019); 10.0.20348.3745 or higher (Server 2022); 10.0.25398.1665 or higher (Server 2022 23h2); 10.0.26100.4270 or higher (Server 2025)

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows Server version is affected from: Server 2016 (build <10.0.14393.8148), Server 2019 (build <10.0.17763.7434), Server 2022 (build <10.0.20348.3745), Server 2022 23h2 (build <10.0.25398.1665), or Server 2025 (build <10.0.26100.4270)
  3. Open Windows Update: Start > Settings > Update & Security > Windows Update
  4. Click 'Check for updates' and wait for available security updates to appear
  5. Install all pending security updates, specifically those labeled for DHCP Server vulnerability CVE-2025-32725
  6. Restart the server if prompted after updates complete
  7. Verify the fix by checking the build version matches or exceeds: 10.0.14393.8148 (Server 2016), 10.0.17763.7434 (Server 2019), 10.0.20348.3745 (Server 2022), 10.0.25398.1665 (Server 2022 23h2), or 10.0.26100.4270 (Server 2025)
  8. Confirm DHCP Server service is running: Open Services console, locate 'DHCP Server', ensure Status is 'Running'
Caveat Standard Windows security update with no expected breaking changes; test in staging environment before production deployment

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

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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