Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY114 SECURITY RECORDS

Microsoft

Microsoft Office 2019

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 Microsoft Office 2019. 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2020-16947 16 Oct 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication 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-2020-1594 11 Sep 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 13.0.0.0 < publication; 15.0.0.0 < publication 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-2020-1332 11 Sep 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 13.0.0.0 < publication; 15.0.0.0 < publication 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-2020-1193 11 Sep 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.0 < publication; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 13.0.0.0 < publication; 15.0.0 < publication 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-2020-1563 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0 < publication; 13.0.0.0 < publication; 15.0.0 < publication 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-2020-1498 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.0 < publication; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 13.0.0.0 < publication; 15.0.0.0 < publication 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-2020-1497 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 16.0.0 < publication; 13.0.0.0 < publication; 15.0.0.0 < publication; 15.0.0 < publication 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-2020-1496 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 16.0.0 < publication; 13.0.0.0 < publication; 15.0.0.0 < publication; 15.0.0 < publication 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-2020-1494 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 16.0.0 < publication; 13.0.0.0 < publication; 15.0.0.0 < publication; 15.0.0 < publication 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-2020-1483 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 15.0.0.0 < publication; 13.0.0.0 < publication 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-2020-1493 17 Aug 2020 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.1 < https://aka.ms/OfficeSecurityReleases; 16.0.0.0 < publication; 15.0.0.0 < publication; 13.0.0.0 < publication 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-1204 14 Aug 2019 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.0 < publication; 16.0.0.0 < publication; 15.0.0.0 < publication; 13.0.0.0 < publication 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-1200 14 Aug 2019 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.0 < publication; 16.0.0.0 < publication; 15.0.0.0 < publication; 13.0.0.0 < publication 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-1199 14 Aug 2019 19.0.0 < https://aka.ms/OfficeSecurityReleases; 16.0.0 < publication 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.