dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32074

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 memory corruption vulnerability exists in the Windows Projected File System (ProjFS) component. This allows a locally authenticated attacker with existing access to exploit the memory corruption and achieve privilege escalation to higher system privileges.

MitigationApply the Microsoft security update for CVE-2026-32074 when released; given the high severity and local privilege escalation vector, prioritize deployment on affected Windows systems, particularly those running ProjFS-enabled roles.

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. Determine your Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19045.7184)
    Affected if The build number is lower than any of the thresholds: 17763.8644 (Win 10 1809/Server 2019), 19044.7184 (Win 10 21h2), 19045.7184 (Win 10 22h2), 22631.6936 (Win 11 23h2), 26100.8246 (Win 11 24h2), 26200.8246 (Win 11 25h2), or 28000.1836 (Win 11 26h1)
  2. Verify ProjFS component availability
    Check if the Projected File System filter driver is loaded by running 'fltmc filters' in an elevated command prompt and look for 'ProjFS' in the output, or query the registry at 'HKLM\SYSTEM\CurrentControlSet\Services\ProjFS'
    Affected if The ProjFS filter driver is present on the system (the vulnerability exists in this component even if not actively used by the current user)
  3. Confirm Windows feature state
    Run 'dism /Online /Get-Features /FeatureName:Microsoft-Windows-ProjectedFileSystem' to check if the ProjFS feature is enabled
    Affected if The ProjFS feature shows as Enabled or Enabled with Pending State (the flaw is in the ProjFS component code path)

You are affected if your Windows build version falls below the threshold for your specific Windows release AND the ProjFS component 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 Microsoft security update for CVE-2026-32074 when released; given the high severity and local privilege escalation vector, prioritize deployment on affected Windows systems, particularly those running ProjFS-enabled roles.

Recommended fix High confidence

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+ | Windows Server 2019: 10.0.17763.8644+

  1. Identify the current Windows version by running `winver` or checking System Information
  2. Determine which Windows 10 or 11 version or Windows Server 2019 is installed from the list of affected versions
  3. Apply the appropriate Windows Update patch for your version, or manually download and install the specific cumulative update from Microsoft Update Catalog that contains the fix
  4. For Windows 10 1809: install update version 10.0.17763.8644 or later
  5. For Windows 10 21h2: install update version 10.0.19044.7184 or later
  6. For Windows 10 22h2: install update version 10.0.19045.7184 or later
  7. For Windows 11 23h2: install update version 10.0.22631.6936 or later
  8. For Windows 11 24h2: install update version 10.0.26100.8246 or later
Caveat Standard Windows cumulative update risks apply (rare compatibility issues with third-party drivers or software)

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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