cve.bz

CVE-2019-1297 Microsoft Excel Remote Code Execution Vulnerability

8.8 highKEVEPSS 22%Fix available

High (8.8) in Microsoft Excel. In CISA KEV since 2022-03-03. EPSS 22% estimated probability of exploitation activity in the next 30 days.

On this page
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'.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
22% (unchanged from 22% a week ago; 22% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-03-03, due 2022-03-17
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-1297 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-1297?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-1297?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-1297 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:excel2010:sp2
microsoft:excel2013:sp1
microsoft:excel2016
microsoft:office2016
microsoft:office2019

References

Check your stackJSON