dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32170

MEDIUM · 6.7 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
67/100
Remediation priority · Elevated

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
Double free in Windows Rich Text Edit 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 · moderate confidence

A double-free vulnerability exists in Windows Rich Text Edit control where memory is improperly deallocated twice, leading to memory corruption. An authenticated local attacker can exploit this to gain elevated privileges on the affected system.

MitigationApply Microsoft security updates for this vulnerability through standard patch management processes. Limit local access to trusted users to reduce the attack surface.

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 1607Operating system
Affected:< 10.0.14393.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 build version
    Run `winver` or `systeminfo` to view the installed Windows version and build number. Alternatively, run `wmic os get Caption,Version,BuildNumber` for structured output.
    Affected if The build number cannot be determined or does not match any of the listed affected versions.
  2. Compare Windows 10 1607 builds
    If the OS is Windows 10 Version 1607, verify the build number is below 10.0.14393.9140.
    Affected if Build number is below 14393.9140 on Windows 10 1607.
  3. Compare Windows 10 1809 builds
    If the OS is Windows 10 Version 1809, verify the build number is below 10.0.17763.8755.
    Affected if Build number is below 17763.8755 on Windows 10 1809.
  4. Compare Windows 10 21h2 and 22h2 builds
    If the OS is Windows 10 21h2 or 22h2, verify the build numbers. 21h2 must be below 10.0.19044.7291. 22h2 must be below 10.0.19045.7291.
    Affected if Build number is below 19044.7291 on Windows 10 21h2, or below 19045.7291 on Windows 10 22h2.
  5. Compare Windows 11 builds
    If the OS is Windows 11, identify the specific version (23h2, 24h2, 25h2, or 26h1) and verify the build number. 23h2: below 22631.7079. 24h2: below 26100.8390. 25h2: below 26200.8390. 26h1: below 28000.2113.
    Affected if Build number is below the version-specific threshold for the detected Windows 11 release.

A system is affected if the installed Windows build number falls below the specific threshold listed for its version and release.

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.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply Microsoft security updates for this vulnerability through standard patch management processes. Limit local access to trusted users to reduce the attack surface.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9140 | Windows 10 1809: 10.0.17763.8755 | Windows 10 21h2: 10.0.19044.7291 | Windows 10 22h2: 10.0.19045.7291 | Windows 11 23h2: 10.0.22631.7079 | Windows 11 24h2: 10.0.26100.8390 | Windows 11 25h2: 10.0.26200.8390 | Windows 11 26h1: 10.0.28000.2113

  1. Identify the current Windows version by running `winver` or checking System Information
  2. Determine which Windows version family applies (Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, 26h1)
  3. Apply the appropriate Microsoft security update that includes the fix for CVE-2026-32170, or upgrade to a later Windows release that includes the patched version
  4. Restart the system after applying the update to ensure the vulnerability is remediated
  5. Verify the installed version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks - ensure backups and compatibility testing for business-critical applications before deploying

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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