Code execution via out-of-bounds memory read
Published Jun 9, 2026 · Updated Jun 9, 2026
Out-of-bounds read in Microsoft Office Word allows attackers to execute code locally after a user opens a malicious document. Word reads beyond an allocated memory object's bounds while handling attacker-controlled data, but Microsoft has not disclosed the affected parser or pointer path. The attack requires no prior privileges but requires user interaction, and successful exploitation runs code with the victim user's rights.
Summary
What happened
Out-of-bounds read in Microsoft Office Word allows attackers to execute code locally after a user opens a malicious document. Word reads beyond an allocated memory object's bounds while handling attacker-controlled data, but Microsoft has not disclosed the affected parser or pointer path. The attack requires no prior privileges but requires user interaction, and successful exploitation runs code with the victim user's rights.
The record
- CVE
- CVE-2026-45457
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-125, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE 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=-
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