dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-32718

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
80/100
Remediation priority · High
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
Integer overflow or wraparound in Windows SMB allows an authorized attacker to elevate privileges locally.

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

Integer overflow or wraparound vulnerability in Windows SMB (Server Message Block) protocol allows a locally authenticated, authorized attacker to elevate privileges to higher integrity levels. The flaw exists in SMB's handling of certain network operations or data structures where integer arithmetic wraps around, potentially leading to memory corruption that can be exploited for privilege escalation.

MitigationApply Microsoft security updates for CVE-2025-32718 to all affected Windows systems, prioritizing domain controllers and file servers that handle SMB connections. Verify SMB functionality post-patch in staging before production deployment.

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 1507Operating system
Affected:< 10.0.10240.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Retrieve Windows version and build number
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The displayed build number falls below any of these thresholds: 10240.21034 (Win10 1507), 14393.8148 (Win10 1607), 17763.7434 (Win10 1809), 19044.5965 (Win10 21h2), 19045.5965 (Win10 22h2), 22621.5472 (Win11 22h2), 22631.5472 (Win11 23h2), 26100.4270 (Win11 24h2)
  2. Confirm SMB service status
    Run 'Get-Service -Name SmbServer' in PowerShell or check Services.msc for 'Server' or 'SMB 1.0/CIFS File Sharing Support'
    Affected if SMB services are enabled and running, as the vulnerability exists in SMB protocol handling

You are affected if your Windows version build number is lower than the corresponding threshold for your Windows release branch and SMB is enabled.

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.10240.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply Microsoft security updates for CVE-2025-32718 to all affected Windows systems, prioritizing domain controllers and file servers that handle SMB connections. Verify SMB functionality post-patch in staging before production deployment.

Recommended fix Moderate confidence

Upgrade to build ≥10.0.10240.21034 (Win10 1507), ≥10.0.14393.8148 (Win10 1607), ≥10.0.17763.7434 (Win10 1809), ≥10.0.19044.5965 (Win10 21h2), ≥10.0.19045.5965 (Win10 22h2), ≥10.0.22621.5472 (Win11 22h2), ≥10.0.22631.5472 (Win11 23h2), ≥10.0.26100.4270 (Win11 24h2)

  1. Check the current Windows version and build number (run 'winver' or 'systeminfo' and note the build, e.g., 10.0.19045.x).
  2. Identify the threshold build for your Windows edition from the CVE: Windows 10 1507 ≥10.0.10240.21034, Windows 10 1607 ≥10.0.14393.8148, Windows 10 1809 ≥10.0.17763.7434, Windows 10 21h2 ≥10.0.19044.5965, Windows 10 22h2 ≥10.0.19045.5965, Windows 11 22h2 ≥10.0.22621.5472, Windows 11 23h2 ≥10.0.22631.5472, Windows 11 24h2 ≥10.0.26100.4270.
  3. If your current build is lower than the threshold, apply the Microsoft security update for CVE-2025-32718 (available via Windows Update or Microsoft Update Catalog) that raises the build to the fixed version.
  4. Restart the system after applying the update.
  5. Verify the new build number meets or exceeds the required threshold using 'winver'.
Caveat Applying the security update requires a system restart; verify compatibility with line‑of‑business applications before updating.

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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