CVE-2019-1331 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 7y ago modified 4mo ago also EUVD-2019-9890
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.7%
- EPSS 19.7% 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'. This CVE ID is unique from CVE-2019-1327.
Patch / fix
Is CVE-2019-1331 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
19.72% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 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 Online Server
- Microsoft Microsoft SharePoint Enterprise Server
- Microsoft Office 365 ProPlus
- Microsoft Excel Services on Microsoft SharePoint Server 2010 Service Pack 2
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-1331
patch, vendor-advisory
Sources
- CVE List CVE-2019-1331
- NVD CVE-2019-1331
Fencer Intel 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.