Code execution via improper Media Foundation object handling
Published May 21, 2020 · Updated Aug 19, 2026
Memory corruption in Microsoft Windows Media Foundation allows remote attackers to execute code through crafted documents or webpages. The framework improperly handles objects in memory while parsing attacker-controlled content; Microsoft has not disclosed the specific object type or faulty operation. Execution requires a user to open the document or visit the webpage, after which code runs with that user's rights and can alter data or accounts.
Summary
What happened
Memory corruption in Microsoft Windows Media Foundation allows remote attackers to execute code through crafted documents or webpages. The framework improperly handles objects in memory while parsing attacker-controlled content; Microsoft has not disclosed the specific object type or faulty operation. Execution requires a user to open the document or visit the webpage, after which code runs with that user's rights and can alter data or accounts.
The record
- CVE
- CVE-2020-1028
- Published
- May 21, 2020
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-787, T1204.002, T1189
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 19, 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 <publication
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