Current-user code execution via object memory corruption
Published May 21, 2020 · Updated Aug 19, 2026
Memory corruption in Microsoft's VBScript engine used by Internet Explorer 9 and 11 allows remote attackers to execute code as the current user. The engine mishandles objects in memory while processing crafted script content; Microsoft has not disclosed the specific object operation or narrower code locus. Exploitation requires a user to open attacker-controlled web content or a document hosting the IE engine, and administrative users expose the entire system.
Summary
What happened
Memory corruption in Microsoft's VBScript engine used by Internet Explorer 9 and 11 allows remote attackers to execute code as the current user. The engine mishandles objects in memory while processing crafted script content; Microsoft has not disclosed the specific object operation or narrower code locus. Exploitation requires a user to open attacker-controlled web content or a document hosting the IE engine, and administrative users expose the entire system.
The record
- CVE
- CVE-2020-1058
- Published
- May 21, 2020
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Internet Explorer 11
- Classifications
- CWE-787, T1189, T1203
- Attack vector
- network
- 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=1.0.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