Local information disclosure via out-of-bounds read
Published Jun 10, 2025 · Updated Feb 20, 2026
Out-of-bounds read in Windows Storage Management Provider allows local users to disclose memory contents on affected Windows builds. Microsoft identifies the weakness class but has not published the specific code locus, input path, or bounds-checking failure behind the unintended read. Exploitation requires local low-privilege access and no user interaction; the reported consequence is memory disclosure without modification or service interruption.
Summary
What happened
Out-of-bounds read in Windows Storage Management Provider allows local users to disclose memory contents on affected Windows builds. Microsoft identifies the weakness class but has not published the specific code locus, input path, or bounds-checking failure behind the unintended read. Exploitation requires local low-privilege access and no user interaction; the reported consequence is memory disclosure without modification or service interruption.
The record
- CVE
- CVE-2025-32719
- Published
- Jun 10, 2025
- Updated
- Feb 20, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 2025CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.10240.0 <10.0.10240.21034
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo