Executive Summary

Use after free in Windows Projected File System allows an authorized attacker to elevate privileges locally.

Overview

7.8
CVSS HIGH
Important
MS Severity
Not Exploited
MS Exploit Status
Less Likely
MS Exploit Likelihood
Category Elevation of Privilege
Released Apr 14 2026
Last Updated Apr 14 2026
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known
EPSS Score 0.00258 — 0.17505 percentile
NVD CVSS 7.8 HIGH — matches MSRC

Verified Attribution

Report-backed
Verified binaryprjflt.sys
FunctionPrjfScheduleExpansionWorkItem
WeaknessCWE-416
SourceBug-hunter LPE writeup (shared collection)
NoteExpansion work-item UAF via ObfDereferenceObject on the file object.

Binary/function confirmed from a public vendor or researcher report; this pin overrides the keyword heuristic.

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
ATTACK VECTOR
Local
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
Low
USER INTERACTION
None
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Unproven
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 6.8

EPSS Score

0.00258
probability of exploitation in the next 30 days
0.17505 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

23 affected products
Product KB Article Severity Impact Restart Required
Windows 10 Version 1809 for 32-bit Systems 5082123 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1809 for x64-based Systems 5082123 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for 32-bit Systems 5082200 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for ARM64-based Systems 5082200 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for x64-based Systems 5082200 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for 32-bit Systems 5082200 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for ARM64-based Systems 5082200 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for x64-based Systems 5082200 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for ARM64-based Systems 5082052 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for x64-based Systems 5082052 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for ARM64-based Systems 5083769 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for x64-based Systems 5083769 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 25H2 for ARM64-based Systems 5083769 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 25H2 for x64-based Systems 5083769 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 26H1 for ARM64-based Systems 5083768 (Security Update) Important Elevation of Privilege Yes
Windows 11 version 26H1 for x64-based Systems 5083768 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 5082123 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 (Server Core installation) 5082123 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 5082142 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 (Server Core installation) 5082142 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022, 23H2 Edition (Server Core installation) 5082060 (Security Update) Important Elevation of Privilege Yes
Windows Server 2025 5082063 (Security Update) Important Elevation of Privilege Yes
Windows Server 2025 (Server Core installation) 5082063 (Security Update) Important Elevation of Privilege Yes

Patches

8 patches
Article Type Restart
5082123 Security Update Yes
5082200 Security Update Yes
5082052 Security Update Yes
5083769 Security Update Yes
5083768 Security Update Yes
5082142 Security Update Yes
5082060 Security Update Yes
5082063 Security Update Yes

Patch Diff

ghidriff · prjflt.sys (KB5083769)

Reference-count underflow use-after-free (CWE-416) via cleanup asymmetry in the Windows Projected File System minifilter prjflt.sys PrjfScheduleExpansionWorkItem, local EoP. The function allocates a generic work item (FltAllocateGenericWorkItem), then ObfReferenceObject(FileObject) +1, then FltQueueGenericWorkItem. Two failure paths shared one cleanup block (LABEL_10/LABEL_14) that unconditionally ObfDereferenceObject(FileObject)'d: on queue-insert failure the ref was already taken (symmetric), but on ALLOCATION failure the goto reaches the same cleanup before ObfReferenceObject ran -> a dereference of a FILE_OBJECT never referenced here, so its refcount ends 1 lower than actual. Forcing FltAllocateGenericWorkItem to fail (pool pressure) drives the count to 0 while other paths hold the object -> free -> kernel UAF (reporter PoC reaches it via NtCreateFile on a ProjFS root: PrjfPostCreate -> PrjfProcessOpenWithinVirtualizationRoots -> PrjfExpandAndWait -> PrjfLaunchExpansion -> PrjfScheduleExpansionWorkItem). Diff of prjflt.sys 10.0.26100.8115 -> .8246 (Apr 14 2026, KB5083769) confirms the fix: gated behind CFR flag Feature_2428439865, a bool flag (init false) is set true only after ObfReferenceObject, and the shared-cleanup ObfDereferenceObject is guarded by `!feature || flag`. This is the ProjFS twin of the wcifs.sys cleanup-asymmetry bug CVE-2026-33098. Note: our diff shows Feature_2428439865 (build/arch).

Pre-patch version 10.0.26100.8115 Download
Post-patch version 10.0.26100.8246 Download
Function Address Change Note
PrjfScheduleExpansionWorkItem code change code (ref-tracking flag guards shared-cleanup deref, CFR-gated) Pre: alloc-fail -> goto shared cleanup (LABEL_10/14) -> unconditional ObfDereferenceObject(FileObject) with no matching ObfReferenceObject -> refcount underflow -> UAF. Post (Feature_2428439865): bVar13=false, set true right after ObfReferenceObject; cleanup does ObfDereferenceObject only if `!feature || bVar13`.
Feature_2428439865 gate added (CFR gate) CFR flag gating the guarded dereference; original unconditional deref still ships when disabled.
View full diff report View RCA report

Root Cause Analysis

CVE-2026-32078 — Windows Projected File System prjflt.sys Reference-Count Underflow in PrjfScheduleExpansionWorkItem → Use-After-Free


Summary

Product Windows — prjflt.sys (Windows Projected File System / ProjFS minifilter)
CVE ID CVE-2026-32078
Impact Elevation of Privilege
MSRC severity Important
CVSS 7.8 / 6.8 — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE CWE-416: Use After Free (cleanup-asymmetry reference-count underflow)
Delivery Local — force the work-item allocation to fail during a ProjFS placeholder expansion
KB / Fixed build KB5083769 — prjflt.sys 10.0.26100.8246 (Win11 24H2 x64)
Patch Date April 14, 2026 (2026-Apr)
Pre-patch binary prjflt.sys 10.0.26100.8115 — SHA256 51d12b128e33bc0110344cea5c6374192d525c9f918666c9886a57c5486e5d3d
Post-patch binary prjflt.sys 10.0.26100.8246 — SHA256 6eeb5961eb44704a1515a3df15bbf02ce4e63c55b46fb00158a5d65c7b4fd555
Feature flag Feature_2428439865 — the fix is CFR-gated
Exploitability Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC)

Product Description

prjflt.sys is the Windows Projected File System (ProjFS) minifilter. PrjfScheduleExpansionWorkItem asynchronously queues a placeholder-expansion work item: it allocates a generic work item, takes a reference on the FILE_OBJECT, and queues the work. It is reached from the IRP_MJ_CREATE post-callback (PrjfPostCreate → PrjfProcessOpenWithinVirtualizationRoots → PrjfExpandAndWait → PrjfLaunchExpansion).


Vulnerability Summary

The function has two failure points sharing one cleanup block (LABEL_10 / LABEL_14) that unconditionally calls ObfDereferenceObject(FileObject):

// PrjfScheduleExpansionWorkItem (10.0.26100.8115) — PRE-PATCH, from the reporter PoC
GenericWorkItem = FltAllocateGenericWorkItem();
if ( !GenericWorkItem ) { Status = 0xC000009A; goto LABEL_10; }   // *** alloc fail: no ref taken yet ***
ObfReferenceObject(FileObject);                                   // ref +1 (only on alloc success)
Status = FltQueueGenericWorkItem(..., FileObject);
if ( Status < 0 ) { FltFreeGenericWorkItem(GenericWorkItem);
LABEL_10:
LABEL_14:
    _InterlockedDecrement(&ExpansionContext->RefNo3);
    ObfDereferenceObject(FileObject);                             // *** unconditional deref ***
    return Status;
}

On the queue-failure path the reference was already taken, so the dereference is symmetric. But on the allocation-failure path the code gotos the same cleanup before ObfReferenceObject ran, so it dereferences a FILE_OBJECT that was never referenced here — dropping its refcount by one too many. Forcing the allocation to fail repeatedly (memory pressure) drives the count toward 0 while other paths still hold the object, freeing it → kernel use-after-free (the reporter’s PoC reaches it directly via NtCreateFile on a ProjFS root). This is the ProjFS twin of the same cleanup-asymmetry bug in wcifs.sys (CVE-2026-33098).


Prerequisites and Constraints

  • Local, low-privileged (PR:L, AV:L, AC:L); the path is reached by opening a file under a ProjFS virtualization root (placeholder expansion).
  • Induce FltAllocateGenericWorkItem failures (pool pressure) so the allocation-failure cleanup over-releases the FILE_OBJECT refcount.
  • Underflow to zero with live references → free → UAF.

Vulnerability Details

Root Cause

Two error paths with different resource-acquisition states (reference taken vs not) merged into one cleanup block via goto, so the shared unconditional ObfDereferenceObject over-releases on the allocation-failure path — a reference-count underflow.

The patch (confirmed — diff, .8115 → .8246)

Gated behind Feature_2428439865, the fix adds a ref-taken flag initialized false and set true only immediately after ObfReferenceObject; the shared cleanup dereference is guarded so it runs only when a reference was actually taken:

// PrjfScheduleExpansionWorkItem (10.0.26100.8246) — PATCHED, feature-enabled branch (from our diff)
bVar13 = false;
...
ObfReferenceObject(FileObject);
bVar13 = Feature_2428439865__private_IsEnabledDeviceUsage() != 0;   // *** set true only after the ref ***
...
if ( Feature_2428439865__private_IsEnabledDeviceUsage() == 0 || bVar13 )   // *** deref only if ref taken ***
    ObfDereferenceObject(FileObject);

On allocation failure (bVar13 == false) the dereference is skipped, keeping the FILE_OBJECT refcount balanced.

Patch Completeness Assessment

CFR-gated behind Feature_2428439865. The guarded dereference runs only when the flag is enabled; the original unconditional deref still ships when disabled. Verify Feature_2428439865 is enabled to confirm the fix is live.


Detection Guidance

Behavioural. Opening files under ProjFS virtualization roots under pool pressure to force FltAllocateGenericWorkItem failures; refcount-underflow / UAF bugchecks in prjflt!PrjfScheduleExpansionWorkItem / FILE_OBJECT teardown on unpatched/flag-disabled builds.

Config. The fix is CFR-gated — confirm Feature_2428439865 is enabled.


References

  • MSRC advisory — CVE-2026-32078 (Windows Projected File System Elevation of Privilege), released 2026-04-14, KB5083769.
  • Full binary diff: /data/patch_diffs/prjflt_sys-cve-2026-32078-ghidriff.md
  • Same cleanup-asymmetry pattern: CVE-2026-33098 (wcifs.sys WcScheduleExpansionWorkItem).

Attack Path

An allocation-failure path dereferences a FILE_OBJECT it never referenced, underflowing the refcount to a free-while-in-use

Attack path for CVE-2026-32078 An allocation-failure path dereferences a FILE_OBJECT it never referenced, underflowing the refcount to a free-while-in-use 01 — ENTRY Local user opens a file under a ProjFS virtualization root prjflt.sys PrjfPostCreate -> ... -> PrjfScheduleExpansionWorkItem queues a placeholder-expansion work item, referencing the FILE_OBJECT. AV:L/PR:L/AC:L. 02 — CONTROLLED INPUT Induce FltAllocateGenericWorkItem failures under pool pressure On allocation failure the code goto's the shared cleanup before ObfReferenceObject runs. 03 — PATH The shared cleanup unconditionally ObfDereferenceObject(FileObject) On the alloc-failure path no reference was taken, but LABEL_10/LABEL_14 still decrements - an over-release. 04 — MISSING CHECK Cleanup asymmetry: deref without a matching ref -> refcount underflow (CWE-416) Each allocation failure leaves the FILE_OBJECT refcount one lower than actual; repeated failures drive it toward 0. 05 — PRIMITIVE Refcount reaches 0 with live references -> FILE_OBJECT freed -> kernel UAF -> EoP Other paths still use the prematurely freed object. The Apr 2026 fix (Feature_2428439865) tracks whether the ref was taken and dereferences only then.

Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.

Exploits & PoC

Detection Rules

Acknowledgments

ChenJian with Sea Security Orca Team