Remote code execution via crafted graphics file
Published Sep 15, 2021 · Updated Aug 10, 2026
Remote code execution in Microsoft Office 2013, 2016, and 2019 allows remote attackers to execute code when a user opens a crafted document. The flaw resides in Office graphics processing, but Microsoft has not published the specific parsing operation or memory-safety failure that permits control of execution. User interaction is required, and the documented impact is execution with the privileges of the Office process; no network-service attack path is described.
Summary
What happened
Remote code execution in Microsoft Office 2013, 2016, and 2019 allows remote attackers to execute code when a user opens a crafted document. The flaw resides in Office graphics processing, but Microsoft has not published the specific parsing operation or memory-safety failure that permits control of execution. User interaction is required, and the documented impact is execution with the privileges of the Office process; no network-service attack path is described.
The record
- CVE
- CVE-2021-38658
- Published
- Sep 15, 2021
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office 2016
- Classifications
- T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2021CVE 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 <5215.1000
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