Code execution via OLE heap buffer overflow
Published Nov 11, 2025 · Updated Feb 26, 2026
Heap-based buffer overflow in Microsoft Windows OLE allows local users to execute code after required user interaction. Microsoft has not disclosed the affected OLE routine or the incorrect memory operation beyond identifying a heap-based buffer overflow. Exploitation requires local access and user interaction; successful exploitation runs attacker-controlled code in the affected user context.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows OLE allows local users to execute code after required user interaction. Microsoft has not disclosed the affected OLE routine or the incorrect memory operation beyond identifying a heap-based buffer overflow. Exploitation requires local access and user interaction; successful exploitation runs attacker-controlled code in the affected user context.
The record
- CVE
- CVE-2025-60714
- Published
- Nov 11, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 11, 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.17763.0 <10.0.17763.8027
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