A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory, aka '
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Microsoft Excel is affected by this vulnerability, which stems from improper handling of objects in memory. An attacker who successfully exploits it could execute arbitrary code remotely on a victim's system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory, aka 'Microsoft Excel Remote Code Execution Vulnerability'.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Microsoft Microsoft Excel
2010 Service Pack 2 (32-bit editions), 2010 Service Pack 2 (64-bit editions), 2013 Service Pack 1 (32-bit editions), 2013 Service Pack 1 (64-bit editions), 2013 RT Service Pack 1, 2016 (32-bit edition), 2016 (64-bit edition)
- Microsoft Microsoft Office
2016 for Mac, 2019 for 32-bit editions, 2019 for 64-bit editions, 2019 for Mac
- Microsoft Office 365 ProPlus
32-bit Systems, 64-bit Systems