Called exploited 1 days before disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing1d
- Last KEV listing3.8y
- Last sighting4.8y
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Nov 3, 2021
- EUVDENISA, European Unionlisted Nov 3, 2021
- VulnCheck KEVcommercial researchlisted Jan 9, 2018
- CIRCLaggregator, mirrors the abovelisted Nov 3, 2021, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationsecurelist.com/vulnerabilities-and-exploits-in-q2-2026/12109
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationhunt.io/blog/eastern-europe-malicious-infrastructure-report
- reported exploitationmedium.com/@nshcthreatrecon/weekly-threat-intelligence-repor
- reported exploitationsecurelist.ru/cloud-atlas-2026/115682/
- reported exploitationsecurelist.com/vulnerabilities-and-exploits-in-q1-2026/11973
57 public reports collected from VulnCheck and CIRCL, first on Jan 9, 2018. Each links to its original source. We have not verified them.
Description
Microsoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0798.
Required action (CISA)
Apply updates per vendor instructions.
