Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-62462 is a high-severity Buffer Over-read (CWE-126) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-16 (Memory Protection) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-202229
Vulnerability Data
Buffer over-read in Windows Projected File System allows an authorized attacker to elevate privileges locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Buffer over-read in Windows Projected File System enables local privilege escalation, directly mapping to T1068 (Exploitation for Privilege Escalation).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly implements memory safety mechanisms that block buffer over-read exploitation in components such as ProjFS.
Requires prompt application of vendor patches that eliminate the buffer over-read flaw in Windows Projected File System.
Enforces input validation on file-system metadata and data streams, reducing the likelihood of out-of-bounds reads.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly prevent introduction of buffer over-read weaknesses.
Vulnerability identification processes can discover buffer over-read flaws via scanning or review.
Patching or replacing vulnerable software removes known instances of buffer over-read bugs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect buffer over-reads before release.
Secure SDLC mandates input validation and bounds checking that can prevent buffer over-reads.
Application security requirements can specify buffer-size and bounds-checking rules.
Secure architecture principles include memory-safety and bounds-checking design choices.
Secure coding standards directly require bounds-checked buffer access, mitigating over-reads.