dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32069

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.17763.8644 / 10.0.19044.7184 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
Double free in Windows Projected File System 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 Projected File System (ProjFS), a Windows feature that allows virtualizing file system data. The flaw enables a local, authorized attacker to escalate privileges by corrupting memory through double-freeing a memory pointer.

MitigationApply the relevant Microsoft security update when released. In the interim, restrict local user permissions and monitor for suspicious kernel-mode activity.

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 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
Windows Server 2019Operating system
Affected:< 10.0.17763.8644

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. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain your Windows build number
    Affected if Your build number is less than the threshold for your Windows version (e.g., < 10.0.17763.8644 for Windows 10 1809/Server 2019, < 10.0.19044.7184 for Windows 10 21h2, etc.)
  2. Identify Windows version and build
    Run 'ver' at command prompt or check System Properties to determine both your Windows release (e.g., 1809, 21h2, 22h2, 23h2) and exact build number
    Affected if You are on an affected Windows release with a build number below the corresponding threshold
  3. Verify ProjFS feature status
    Run 'Get-WindowsOptionalFeature -Online -FeatureName *ProjFS*' in PowerShell with admin rights, or check 'Projected File System' in Windows Features (optionalfeatures.exe)
    Affected if The Projected File System feature is installed or enabled on your system
  4. Check for ProjFS driver presence
    Run 'driverquery /v | findstr -i projfs' or check for 'mfluap.sys' loaded in memory via 'tasklist /m mfluap.sys'
    Affected if The ProjFS kernel driver (mfluap.sys) is loaded and running

You are likely affected if your Windows build falls within the affected version ranges AND the ProjFS feature or its kernel driver is present on your system.

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.17763.8644 / 10.0.19044.7184 / 10.0.19045.7184 or later
Fixed in 10.0.17763.864410.0.19044.718410.0.19045.7184
Interim mitigation

Apply the relevant Microsoft security update when released. In the interim, restrict local user permissions and monitor for suspicious kernel-mode activity.

Recommended fix High confidence

Apply the latest Windows Security Update containing the CVE-2026-32069 patch via Windows Update

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Ensure the update includes the patch for CVE-2026-32069 (verify KB article from Microsoft Security Response Center)
  4. Restart the system after updates are installed
  5. Verify the installed Windows version meets or exceeds the fixed build numbers: 10.0.17763.8644 (Win10 1809/Server 2019), 10.0.19044.7184 (Win10 21h2), 10.0.19045.7184 (Win10 22h2), 10.0.22631.6936 (Win11 23h2), 10.0.26100.8246 (Win11 24h2), 10.0.26200.8246 (Win11 25h2), or 10.0.28000.1836 (Win11 26h1)
Caveat Standard Windows update risks - ensure backups and compatibility testing for mission-critical systems

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA8.0 h
46.0 hours of engineering $8,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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