Microsoft
Excel
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Excel. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-43106 | 18 Dec 2024 | 16.83 for macOS | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-1297 | 11 Sep 2019 | 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 Office: 2016 for Mac, 2019 for 32-bit editions, 2019 for 64-bit editions, 2019 for Mac; Office 365 ProPlus: 32-bit Systems, 64-bit Systems | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-7262 | 20 Dec 2016 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2009-3129 | 11 Nov 2009 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.