Executive Summary

Buffer over-read 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 Dec 9 2025
Last Updated Dec 9 2025
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known
EPSS Score 0.00392 — 0.32289 percentile
NVD CVSS 7.8 HIGH — matches MSRC

Verified Attribution

Report-backed
Verified binaryprjflt.sys
WeaknessCWE-200
SourceBug-hunter LPE writeup (shared collection)
NotePrjLeak: directory-enumeration info leak (NextEntryOffset/FileNameLength). Exact fn not pinned in writeup.

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.00392
probability of exploitation in the next 30 days
0.32289 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

13 affected products
Product KB Article Severity Impact Restart Required
Windows 10 Version 1809 for 32-bit Systems 5071544 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1809 for x64-based Systems 5071544 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for 32-bit Systems 5071546 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for ARM64-based Systems 5071546 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for x64-based Systems 5071546 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for 32-bit Systems 5071546 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for ARM64-based Systems 5071546 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for x64-based Systems 5071546 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for ARM64-based Systems 5071417 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for x64-based Systems 5071417 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for ARM64-based Systems 5072033 (Security Update) 5072014 (Security Hotpatch Update) Important Elevation of Privilege 5068861 5068966 Base: 7.8 Temporal: 6.8 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 10.0.26100.7462 10.0.26100.7392 Yes None Windows 11 Version 24H2 for x64-based Systems 5072033 (Security Update) 5072014 (Security Hotpatch Update) Important Elevation of Privilege 5068861 5068966 Base: 7.8 Temporal: 6.8 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 10.0.26100.7462 10.0.26100.7392 Yes None Windows 11 Version 25H2 for ARM64-based Systems 5072033 (Security Update) 5072014 (Security Hotpatch Update) Important Elevation of Privilege 5068861 5068966 Base: 7.8 Temporal: 6.8 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 10.0.26200.7462 10.0.26200.7392 Yes None Windows 11 Version 25H2 for x64-based Systems 5072033 (Security Update) 5072014 (Security Hotpatch Update) Important Elevation of Privilege 5068861 5068966 Base: 7.8 Temporal: 6.8 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 10.0.26200.7462 10.0.26200.7392 Yes None Windows Server 2019 5071544 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 (Server Core installation) 5071544 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 5071547 (Security Update) 5071413 (Security Hotpatch Update) Important Elevation of Privilege 5068787 5068840 Base: 7.8 Temporal: 6.8 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 10.0.20348.4529 10.0.20348.4467 Yes None Windows Server 2022 (Server Core installation) 5071547 (Security Update) 5071413 (Security Hotpatch Update) Important Elevation of Privilege 5068787 5068840 Base: 7.8 Temporal: 6.8 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 10.0.20348.4529 10.0.20348.4467 Yes None Windows Server 2022, 23H2 Edition (Server Core installation) 5071542 (Security Update) Important Elevation of Privilege Yes

Patches

4 patches
Article Type Restart
5071544 Security Update Yes
5071546 Security Update Yes
5071417 Security Update Yes
5071542 Security Update Yes

Patch Diff

ghidriff · prjflt.sys (KB5072033)

Buffer over-read (CWE-126) in the Windows Projected File System minifilter prjflt.sys enumeration validation/advance mismatch, local EoP info-leak. PrjfValidateNamesInEnumeration validates directory-info entries but, when an entry's NextEntryOffset is 0, it validates only that entry and returns without checking any following entry. PrjfAdvanceToNextEnumEntry, however, when NextEntryOffset is 0, still advances to a next entry by computing FileNameOffset + FileNameLength. PRE: a result buffer with two entries whose first entry has NextEntryOffset==0 is only validated for the first entry, yet PrjfMergeEnumerationResults -> PrjfAdvanceToNextEnumEntry advances to the second, unvalidated entry and PrjfMungeDirectoryEnumerateWithoutShortname copies its (attacker-shaped) data - including leaked pool - to the user buffer. Diff of prjflt.sys 10.0.26100.7309 -> .7462 (Dec 9 2025, KB5072033) confirms the fix: gated behind CFR flag Feature_3797454136, PrjfAdvanceToNextEnumEntry no longer advances past a zero NextEntryOffset - when NextEntryOffset==0 it sets the entry offset to 0xffffffff (stop) instead of adding FileNameOffset+FileNameLength, so validation and advancement stay in agreement.

Pre-patch version 10.0.26100.7309 Download
Post-patch version 10.0.26100.7462 Download
Function Address Change Note
PrjfAdvanceToNextEnumEntry code change code (bounds/validation added, CFR-gated) Pre: on NextEntryOffset==0, ValidateNames stops (validates only entry 1) but AdvanceToNextEnumEntry still advances via FileNameOffset+FileNameLength to an unchecked entry 2 -> its data (incl. leaked pool) copied to user. Post (Feature_3797454136): when NextEntryOffset==0 the offset is set to 0xffffffff (no advance), matching ValidateNames.
Feature_3797454136 gate added (CFR gate) CFR flag gating the added validation; the original unchecked path still ships when disabled.
View full diff report View RCA report

Root Cause Analysis

CVE-2025-62464 — Windows Projected File System prjflt.sys Validate/Advance Mismatch on NextEntryOffset == 0 → Buffer Over-Read


Summary

Product Windows — prjflt.sys (Windows Projected File System / ProjFS minifilter; enumeration merge)
CVE ID CVE-2025-62464
Impact Elevation of Privilege (kernel pool information disclosure)
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-126: Buffer Over-read
Delivery Local — a crafted multi-entry ProjFS directory-enumeration result
KB / Fixed build KB5072033 — prjflt.sys 10.0.26100.7462 (Win11 24H2 x64)
Patch Date December 9, 2025 (2025-Dec)
Pre-patch binary prjflt.sys 10.0.26100.7309 — SHA256 933e0862552cf839905efb55bd867a43881eed1680051096d6b6b5250e5674c8
Post-patch binary prjflt.sys 10.0.26100.7462 — SHA256 2a9350bc757df5a7480494b2faf40813731baf0dd26c6383b6d86f46dee68468
Feature flag Feature_3797454136 — the fix is CFR-gated
Exploitability Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC)

Product Description

When ProjFS merges a directory-enumeration result into the caller’s buffer, it validates each entry with PrjfValidateNamesInEnumeration and walks entries with PrjfAdvanceToNextEnumEntry (driven from PrjfMergeEnumerationResults). Each directory-info entry carries a NextEntryOffset linking to the next entry; a NextEntryOffset of 0 conventionally marks the last entry.


Vulnerability Summary

The validator and the advancer disagreed on what NextEntryOffset == 0 means. PrjfValidateNamesInEnumeration, on reaching an entry whose NextEntryOffset is 0, validates that entry and returns (treating it as the last):

// PrjfValidateNamesInEnumeration (pre) — from the reporter analysis
NextEntryOffset = DirEntry->NextEntryOffset;
if (!NextEntryOffset) return Status;   // stop after this entry

PrjfAdvanceToNextEnumEntry, however, still advanced past a zero NextEntryOffset by computing FileNameOffset + FileNameLength:

// PrjfAdvanceToNextEnumEntry (pre) — from the reporter analysis
if (!NextEntryOffset) EntryOffset = FileNameOffset + FileNameLength; // advance anyway
Context->EntryOffset += EntryOffset;

So for a result buffer holding two entries where the first entry’s NextEntryOffset is 0, only the first entry is validated, yet the merge advances to the second, unvalidated entry and PrjfMungeDirectoryEnumerateWithoutShortname copies its attacker-shaped FileName — including adjacent kernel pool — into the caller’s buffer (CWE-126). Because ProjFS runs in the kernel and the enumeration is reachable locally, the disclosed pool is a local EoP primitive.


Prerequisites and Constraints

  • Local, low-privileged (PR:L, AV:L, AC:L): drive a ProjFS enumeration whose result buffer the attacker shapes.
  • Place two entries in the buffer; set the first entry’s NextEntryOffset = 0 and craft the second entry to over-read.
  • Result: the second entry is copied to the user buffer without validation.

Vulnerability Details

Root Cause

PrjfValidateNamesInEnumeration stopped at NextEntryOffset == 0 while PrjfAdvanceToNextEnumEntry still advanced past it, so an entry could be copied that was never validated.

The patch (confirmed — diff, .7309 → .7462)

Gated behind Feature_3797454136, PrjfAdvanceToNextEnumEntry no longer advances past a zero NextEntryOffset — it sets the running entry offset to 0xffffffff (an invalid/stop marker) instead of adding FileNameOffset + FileNameLength, bringing advancement into agreement with the validator:

// PrjfAdvanceToNextEnumEntry (10.0.26100.7462) — PATCHED, feature-enabled branch (from our diff)
if (Feature_3797454136__private_IsEnabledDeviceUsageNoInline() && NextEntryOffset == 0) {
    *(undefined4 *)(param_1 + 0x30) = 0xffffffff;   // stop; do not advance
}
// else (feature) advance by the checked delta

With advancement halting at NextEntryOffset == 0, the merge can no longer reach an unvalidated entry, closing the over-read.

Patch Completeness Assessment

CFR-gated behind Feature_3797454136. The stop-on-zero behaviour runs only when the flag is enabled; the original advancing path still ships when disabled. Verify Feature_3797454136 is enabled to confirm the fix is live.


Detection Guidance

Behavioural. ProjFS enumeration result buffers with a mid-buffer NextEntryOffset == 0 followed by further entry data; over-read / pool-read anomalies from prjflt!PrjfAdvanceToNextEnumEntry / PrjfMungeDirectoryEnumerateWithoutShortname on unpatched/flag-disabled builds.

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


References

  • MSRC advisory — CVE-2025-62464 (Windows Projected File System Elevation of Privilege), released 2025-12-09, KB5072033.
  • Full binary diff: /data/patch_diffs/prjflt_sys-kb5072033-dec2025-ghidriff.md
  • Related same-KB ProjFS enumeration info-leaks: CVE-2025-62462, CVE-2025-62467, CVE-2025-55233.

Attack Path

Enumeration validation stops at a zero NextEntryOffset but advancement does not, so a second unvalidated entry is copied to the user

Attack path for CVE-2025-62464 Enumeration validation stops at a zero NextEntryOffset but advancement does not, so a second unvalidated entry is copied to the user 01 — ENTRY Local user drives a ProjFS directory enumeration with a crafted multi-entry result prjflt.sys validates entries in PrjfValidateNamesInEnumeration then advances via PrjfAdvanceToNextEnumEntry. AV:L/PR:L/AC:L. 02 — CONTROLLED INPUT First entry sets NextEntryOffset = 0 with a second entry following in the buffer Validation treats NextEntryOffset==0 as the last entry and returns after checking only entry 1. 03 — MISSING CHECK Advance logic still steps to the second, unvalidated entry (CWE-126) PrjfAdvanceToNextEnumEntry computes FileNameOffset+FileNameLength when NextEntryOffset==0, moving to entry 2. 04 — PATH The unvalidated second entry is copied to the user buffer PrjfMergeEnumerationResults / PrjfMungeDirectoryEnumerateWithoutShortname memmove entry 2's FileName (incl. leaked pool) to user. 05 — PRIMITIVE Kernel pool disclosed to the caller -> info-leak / EoP The Dec 2025 fix (Feature_3797454136) stops advancement at NextEntryOffset==0, keeping validation and advance in sync.

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