CVE-2019-1297 kev in the critical feed json
A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory, aka…
published 2019-09-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-9862
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Exploited
- added 2022-03-03
- epss
- 21.8%
- EPSS 21.8% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
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'.
Patch / fix
cisa required action Apply updates per vendor instructions.
Timeline
- Published
- Added to CISA KEV
- CISA patch deadline
- CISA SSVC: exploitation active
Known exploited
- Added
- 4 y ago
- Patch by
- 2022-03-17 (4 y ago)
- Ransomware
- Not known
- Required action
- Apply updates per vendor instructions.
- Vendor, product
- Microsoft, Excel
- CISA name
- Microsoft Excel Remote Code Execution Vulnerability
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- no
- Technical impact
- total
- Assessed
- 21 mo ago
Exploit prediction
21.80% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Microsoft Excel
- Microsoft Microsoft Office
- Microsoft Office 365 ProPlus
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-1297
patch, vendor-advisory
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1297
government-resource, us-government-resource
Sources
- CVE List CVE-2019-1297
- NVD CVE-2019-1297
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.