Local code execution via global-memory use-after-free
Published Oct 14, 2025 · Updated Feb 26, 2026
Use-after-free in Inbox COM Objects in Microsoft Windows allows local users to execute arbitrary code after user interaction. Microsoft identifies global memory as the affected area but has not disclosed which COM object frees or later reuses the memory, or what input triggers the stale access. Exploitation requires user interaction and high-complexity conditions beyond the attacker's control; successful code execution occurs on the affected Windows system.
Summary
What happened
Use-after-free in Inbox COM Objects in Microsoft Windows allows local users to execute arbitrary code after user interaction. Microsoft identifies global memory as the affected area but has not disclosed which COM object frees or later reuses the memory, or what input triggers the stale access. Exploitation requires user interaction and high-complexity conditions beyond the attacker's control; successful code execution occurs on the affected Windows system.
The record
- CVE
- CVE-2025-58734
- Published
- Oct 14, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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.21161
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