Code execution via use-after-free memory reuse
Published Aug 8, 2023 · Updated Aug 10, 2026
Use-after-free in Microsoft Outlook in affected Office releases allows attackers to execute code after required user interaction. Microsoft identifies reuse of freed memory but does not disclose the affected object, function, or content-processing path. The required interaction is documented, but Microsoft does not publicly describe the trigger content or any further environmental gate.
Summary
What happened
Use-after-free in Microsoft Outlook in affected Office releases allows attackers to execute code after required user interaction. Microsoft identifies reuse of freed memory but does not disclose the affected object, function, or content-processing path. The required interaction is documented, but Microsoft does not publicly describe the trigger content or any further environmental gate.
The record
- CVE
- CVE-2023-36895
- Published
- Aug 8, 2023
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office 2016
- Classifications
- CWE-416, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Aug 10, 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=16.0.0 <16.0.5408.1002
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