dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32070

HIGH · 7.0 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Use after free in Windows Common Log File System Driver 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

A use-after-free vulnerability exists in the Windows Common Log File System Driver (CLFS.sys). This memory corruption flaw allows a locally authenticated attacker to exploit freed memory to elevate their privileges to SYSTEM level, potentially executing arbitrary code in kernel context.

MitigationApply the Microsoft security update for CVE-2026-32070 via Windows Update or manually download the patch from the Microsoft Security Update Catalog. Prioritize systems with exposed attack surfaces.

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.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Determine Windows build number
    Open Command Prompt or PowerShell and run `winver` or execute `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`. Alternatively, run `ver` command to get the build number directly.
    Affected if The displayed build number is lower than the threshold for your Windows version (see version-specific thresholds below)
  2. Identify Windows release version family
    From the OS name/version output, determine whether the system is Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, or 26h1.
    Affected if The system runs any of the affected Windows versions listed in the CVE
  3. Compare build number against CVE thresholds
    Match your detected build number to the specific threshold: Windows 10 1607 requires < 10.0.14393.9060, 1809 requires < 10.0.17763.8644, 21h2 requires < 10.0.19044.7184, 22h2 requires < 10.0.19045.7184, Windows 11 23h2 requires < 10.0.22631.6936, 24h2 requires < 10.0.26100.8246, 25h2 requires < 10.0.26200.8246, 26h1 requires < 10.0.28000.1836.
    Affected if Your installed build number falls below the threshold for your specific Windows release version

If the system runs any of the affected Windows versions and the installed build number is lower than the corresponding threshold, the environment is vulnerable to CVE-2026-32070.

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.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply the Microsoft security update for CVE-2026-32070 via Windows Update or manually download the patch from the Microsoft Security Update Catalog. Prioritize systems with exposed attack surfaces.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9060+ | Windows 10 1809: 10.0.17763.8644+ | Windows 10 21h2: 10.0.19044.7184+ | Windows 10 22h2: 10.0.19045.7184+ | Windows 11 23h2: 10.0.22631.6936+ | Windows 11 24h2: 10.0.26100.8246+ | Windows 11 25h2: 10.0.26200.8246+ | Windows 11 26h1: 10.0.28000.1836+

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 version branch is installed (e.g., 1607, 1809, 21h2, 22h2, 23h2, 24h2, 25h2, or 26h1)
  3. Apply the appropriate Windows Update for your version branch that includes the fix for CVE-2026-32070, or manually download and install the specific KB patch from the Microsoft Update Catalog
  4. Reboot the system after installing the update
  5. Verify the fix was applied by checking the installed updates or running 'systeminfo' to confirm the OS build number matches or exceeds the fixed version for your branch

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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