Executive Summary

Integer overflow or wraparound 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: reparse-data-buffer handling leak (PrjReparseDataBuffer/ReparseDataLength). Exact fn not pinned.

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)

Integer truncation (CWE-190) leading to buffer over-read (CWE-126) in the Windows Projected File System minifilter prjflt.sys PrjfValidateNamesInEnumeration, local EoP info-leak. When validating a returned directory-info entry (e.g. FILE_ID_EXTD_DIR_INFORMATION), PrjfValidateNamesInEnumeration reads the ULONG FileNameLength but truncates it to a USHORT (movzx word ptr [entry+0x3C]) before bounding it (Length = FileNameLength>>1; if Length>0x104 reject) and scanning the name. PRE: because only the low 16 bits are checked, a FileNameLength such as 0x10000C is validated as 0xC, so only the first 0xC bytes of FileName are checked; the downstream copy (PrjfMungeDirectoryEnumerateWithoutShortname -> memmove(dst, Entry->FileName, FileNameLength)) uses the full ULONG 0x10000C, copying the unchecked 0x10000 leaked bytes into the user buffer. Diff of prjflt.sys 10.0.26100.7309 -> .7462 (Dec 9 2025, KB5072033) confirms the fix: gated behind CFR flag Feature_4287139131, PrjfValidateNamesInEnumeration now rejects any entry whose full ULONG FileNameLength exceeds 0xffff (if (0xffff < param_2[2]) return 0xC000000D) before the USHORT truncation, so the validated length matches the copied length.

Pre-patch version 10.0.26100.7309 Download
Post-patch version 10.0.26100.7462 Download
Function Address Change Note
PrjfValidateNamesInEnumeration code change code (bounds/validation added, CFR-gated) Pre: FileNameLength read as USHORT (movzx r8d,word ptr [rbx+3Ch]) so 0x10000c validates as 0xc, but the copier uses the full ULONG -> leaked bytes bypass validation. Post (Feature_4287139131): if the full ULONG FileNameLength (param_2[2] / param_2[0xf]) > 0xffff, return STATUS_INVALID_PARAMETER (0xC000000D) before truncation.
Feature_4287139131 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-62467 — Windows Projected File System prjflt.sys FileNameLength ULONG→USHORT Truncation in PrjfValidateNamesInEnumeration → Buffer Over-Read


Summary

Product Windows — prjflt.sys (Windows Projected File System / ProjFS minifilter; enumeration validation)
CVE ID CVE-2025-62467
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-190: Integer Overflow/Wraparound (truncation) + CWE-126: Buffer Over-read
Delivery Local — a crafted ProjFS directory-enumeration result entry
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_4287139131 — the fix is CFR-gated
Exploitability Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC)

Product Description

PrjfValidateNamesInEnumeration validates each directory-information entry in a ProjFS enumeration result before it is merged into the caller’s buffer. For a FILE_ID_EXTD_DIR_INFORMATION entry the important fields are NextEntryOffset, FileNameLength (a ULONG), and the inline FileName:

typedef struct _FILE_ID_EXTD_DIR_INFORMATION {
    ULONG NextEntryOffset; ULONG FileIndex; /* ... */
    ULONG FileNameLength;                 // entry + 0x3C, ULONG
    ULONG EaSize; ULONG ReparsePointTag; FILE_ID_128 FileId;
    WCHAR FileName[];                     // entry + 0x58
} FILE_ID_EXTD_DIR_INFORMATION;

Vulnerability Summary

Pre-patch, PrjfValidateNamesInEnumeration read FileNameLength as a USHORT before bounding and scanning the name:

movzx   r8d, word ptr [rbx+3Ch]     ; FileNameLength truncated to 16 bits
// pre-patch validation (from the reporter analysis)
FileNameLength = (USHORT)entry->FileNameLength;   // truncated
Length = FileNameLength >> 1;
if (Length > 0x104) return STATUS_OBJECT_NAME_INVALID;
// scan only 'Length' chars of FileName ...

Because only the low 16 bits are validated, a FileNameLength of 0x10000C is checked as 0xC, so only the first 0xC bytes of FileName are validated. The downstream copier, however, uses the full ULONG:

// PrjfMungeDirectoryEnumerateWithoutShortname (and similar)
memmove(OutEntryBuffer->DirInfo.FileName, Entry->FileName, FileNameLength); // 0x10000C

So the validated 0xC bytes plus an unchecked 0x10000 bytes of adjacent kernel pool are copied into the user buffer — a truncation (CWE-190) that bypasses validation and produces a pool over-read (CWE-126) disclosed to the caller.


Prerequisites and Constraints

  • Local, low-privileged (PR:L, AV:L, AC:L): drive a ProjFS enumeration whose result entry the attacker shapes (via the provider/complete-command path).
  • Set a directory entry’s FileNameLength so its low 16 bits pass validation while the full ULONG is large (e.g. 0x10000C).
  • Result: the copier moves the full ULONG length, leaking unvalidated pool bytes.

Vulnerability Details

Root Cause

Validation truncated the ULONG FileNameLength to a USHORT, so the bound it enforced did not match the full-width length used by the copy path.

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

Gated behind Feature_4287139131, PrjfValidateNamesInEnumeration now rejects any entry whose full ULONG FileNameLength exceeds 0xffff before the USHORT truncation, for each directory-information class:

// PrjfValidateNamesInEnumeration (10.0.26100.7462) — PATCHED, feature-enabled branch (from our diff)
if (Feature_4287139131__private_IsEnabledDeviceUsageNoInline() && (0xffff < param_2[2]))
    return 0xC000000D;                 // STATUS_INVALID_PARAMETER (full ULONG length)
uVar8 = (ushort)param_2[2];            // only then narrow for the scan

(The same full-width > 0xffff check is added for the other directory-info classes, e.g. param_2[0xf].) With the full ULONG validated, an over-length name can no longer pass validation while being copied in full, closing the over-read.

Patch Completeness Assessment

CFR-gated behind Feature_4287139131. The full-width check runs only when the flag is enabled; the original truncating check still ships when disabled. Verify Feature_4287139131 is enabled to confirm the fix is live.


Detection Guidance

Behavioural. ProjFS enumeration entries whose FileNameLength high bits are non-zero (full ULONG > 0xffff); over-read / pool-read anomalies from prjflt!PrjfValidateNamesInEnumeration / PrjfMungeDirectoryEnumerateWithoutShortname on unpatched/flag-disabled builds.

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


References

  • MSRC advisory — CVE-2025-62467 (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-62464, CVE-2025-55233.

Attack Path

A ULONG FileNameLength is truncated to USHORT during validation but used in full when copied, so over-length names leak pool to the user buffer

Attack path for CVE-2025-62467 A ULONG FileNameLength is truncated to USHORT during validation but used in full when copied, so over-length names leak pool to the user buffer 01 — ENTRY Local user drives a ProjFS directory enumeration whose result entry it controls prjflt.sys PrjfValidateNamesInEnumeration validates each directory-info entry. AV:L/PR:L/AC:L. 02 — CONTROLLED INPUT Sets a directory entry FileNameLength (ULONG) like 0x10000C The high bits (0x100000) are what will later over-read; the low bits (0xC) pass validation. 03 — MISSING CHECK Validation truncates FileNameLength to USHORT (CWE-190) movzx word ptr [entry+0x3C] checks only 0xC bytes; the 0x10000 tail is never validated. 04 — PATH The copier uses the full ULONG FileNameLength PrjfMungeDirectoryEnumerateWithoutShortname memmove(dst, Entry->FileName, FileNameLength) copies 0x10000C bytes into the user buffer. 05 — PRIMITIVE Unvalidated pool bytes copied to user -> info-leak / EoP The Dec 2025 fix (Feature_4287139131) rejects FileNameLength > 0xffff before truncation.

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