Microsoft Access

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 Access. 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-2018-8312	11 Jul 2018	2013 Service Pack 1 (32-bit editions); 2013 Service Pack 1 (64-bit editions); 2016 (32-bit edition); 2016 (64-bit edition); 2016 Click-to-Run (C2R) for 32-bit editions; 2016 Click-to-Run (C2R) for 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-0903	14 Mar 2018	Microsoft Access 2010 SP2, Microsoft Access 2013 SP1, Microsoft Access 2016, and Microsoft Office 2016 Click-to-Run	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-0799	10 Jan 2018	Microsoft SharePoint Enterprise Server 2013 and Microsoft SharePoint Enterprise Server 2016	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.