Word

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Word. 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-41165	18 Dec 2024	16.83 for macOS	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-36761	12 Sep 2023	Microsoft Office 2019: 19.0.0 < https://aka.ms/OfficeSecurityReleases; Microsoft 365 Apps for Enterprise: 16.0.1 < https://aka.ms/OfficeSecurityReleases; Microsoft Office LTSC 2021: 16.0.1 < https://aka.ms/OfficeSecurityReleases; Microsoft Word 2016: 16.0.1 < 16.0.5413.1000; Microsoft Word 2013 Service Pack 1: 15.0.1 < 15.0.5589.1001	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-2019-0585	8 Jan 2019	Automation Services on Microsoft SharePoint Server 2010 Service Pack 2; 2010 Service Pack 2 (32-bit editions); 2010 Service Pack 2 (64-bit editions); 2016 for Mac; 2019 for 32-bit editions; 2019 for 64-bit editions; 2019 for Mac; Web Apps Server 2010 Service Pack 2	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-2018-8378	15 Aug 2018	Automation Services on Microsoft SharePoint Server 2010 Service Pack 2; 2013 Service Pack 1; Microsoft Office Word Viewer; 2007 Service Pack 3; Enterprise Server 2013 Service Pack 1; Enterprise Server 2016; 2010 Service Pack 2 (32-bit editions); 2010 Service Pack 2 (64-bit editions)	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-2018-8160	9 May 2018	Automation Services on Microsoft SharePoint Server 2010 Service Pack 2; 2010 Service Pack 2 (32-bit editions); 2010 Service Pack 2 (64-bit editions); Compatibility Pack Service Pack 3; Web Apps Server 2010 Service Pack 2	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-2018-1028	12 Apr 2018	Automation Services on Microsoft SharePoint Server 2010 Service Pack 2; Automation Services on Microsoft SharePoint Server 2013 Service Pack 1; 2010 Service Pack 2 (32-bit editions); 2010 Service Pack 2 (64-bit editions); 2013 RT Service Pack 1; 2013 Service Pack 1 (32-bit editions); 2013 Service Pack 1 (64-bit editions); 2016 (32-bit edition)	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-2014-1761	24 Mar 2014	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-2012-2539	12 Dec 2012	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-2006-2492	20 May 2006	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.