Local privilege escalation via Brokering File System use-after-free
Published Jan 14, 2025 · Updated Jun 9, 2026
Use-after-free in Microsoft Brokering File System allows local users on affected Windows releases to elevate privileges. Microsoft identifies the weakness class but has not disclosed the freed object, triggering operation, or memory-reuse sequence in the Brokering File System. Exploitation requires low-privilege local access and a high-complexity condition; successful abuse crosses a security boundary and grants control over protected resources.
Summary
What happened
Use-after-free in Microsoft Brokering File System allows local users on affected Windows releases to elevate privileges. Microsoft identifies the weakness class but has not disclosed the freed object, triggering operation, or memory-reuse sequence in the Brokering File System. Exploitation requires low-privilege local access and a high-complexity condition; successful abuse crosses a security boundary and grants control over protected resources.
The record
- CVE
- CVE-2025-21372
- Published
- Jan 14, 2025
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2025 (Server Core installation)
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 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.26100.0 <10.0.26100.2894
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.
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