dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2025-33050

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 · low confidence

A protection mechanism failure in Windows DHCP Server allows an unauthorized attacker on the network to cause a denial of service, likely by sending malformed requests that trigger the failure in the server's protection logic.

MitigationApply Microsoft security updates for Windows DHCP Server when available; consider network segmentation and access controls to limit exposure to unauthorized DHCP clients.

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. Identify the Windows Server version and build number
    Run `winver` or `systeminfo` from command prompt, or query the registry with `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild`
    Affected if The build number is lower than 14393.8148 (Server 2016), 17763.7434 (Server 2019), 20348.3745 (Server 2022), 25398.1665 (Server 2022 23h2), or 26100.4270 (Server 2025)
  2. Verify if DHCP Server role is installed
    Run `Get-WindowsFeature -Name DHCP` in PowerShell, or check the DHCP Windows service with `sc query DHCP`
    Affected if The DHCP Server role or service is present on the system
  3. Confirm DHCP Server service status
    Run `Get-Service -Name DHCPServer` or `sc query DHCPServer` to check if the service is running
    Affected if The DHCP Server service is running (the vulnerability requires the DHCP Server to be active to be exploitable)

The system is affected if it runs a vulnerable Windows Server version (below the thresholds listed) AND has the DHCP Server role 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 Microsoft security updates for Windows DHCP Server when available; consider network segmentation and access controls to limit exposure to unauthorized DHCP clients.

Recommended fix High confidence

Windows Server 2016: 10.0.14393.8148 or later | Windows Server 2019: 10.0.17763.7434 or later | Windows Server 2022: 10.0.20348.3745 or later | Windows Server 2022 23h2: 10.0.25398.1665 or later | Windows Server 2025: 10.0.26100.4270 or later

  1. 1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. 2. Click 'Check for updates' to ensure you have the latest security patches
  3. 3. If updates are available, select them and click 'Install'
  4. 4. Alternatively, use Windows Server Update Services (WSUS) or Microsoft Update Catalog to manually download and install the specific security update
  5. 5. After installation, restart the server to apply the updates
  6. 6. Verify the DHCP Server service is running and functioning correctly post-reboot
  7. 7. For enterprise environments, test updates in a staging environment before deploying broadly
Caveat Standard Windows security update; DHCP Server functionality should remain intact; test in non-production environment before broad 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-33050 — 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-33050 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