← Search results
CVE-LINKED INVENTORY18 SECURITY RECORDS
Microsoft Corporation
Microsoft Exchange Server
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 Exchange Server. 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-2019-1136 | 29 Jul 2019 | 2010 Service Pack 3; Cumulative Update 12; Cumulative Update 13; Cumulative Update 23 | 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-1084 | 15 Jul 2019 | 2010 Service Pack 3; 2010 Service Pack 2 (32-bit editions); 2010 Service Pack 2 (64-bit editions); 2016 (32-bit edition); 2016 (64-bit edition); 2013 Service Pack 1 (32-bit editions); 2013 Service Pack 1 (64-bit editions); 2013 RT Service Pack 1 | 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-0858 | 9 Apr 2019 | 2019; Cumulative Update 11; Cumulative Update 12; Cumulative Update 22; Cumulative Update 1 | 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-0817 | 9 Apr 2019 | 2010 Service Pack 3; 2019; Cumulative Update 11; Cumulative Update 12; Cumulative Update 22; Cumulative Update 1 | 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-0588 | 8 Jan 2019 | 2010 Service Pack 3 Update Rollup 25; 2013 Cumulative Update 21; 2016 Cumulative Update 10; 2016 Cumulative Update 11; 2019 | 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-0586 | 8 Jan 2019 | 2016 Cumulative Update 10; 2016 Cumulative Update 11; 2019 | 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-8604 | 12 Dec 2018 | 2016 Cumulative Update 10; 2016 Cumulative Update 11 | 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-8448 | 10 Oct 2018 | 2013 Cumulative Update 21; 2016 Cumulative Update 10 | 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-8265 | 10 Oct 2018 | 2013 Cumulative Update 21; 2016 Cumulative Update 10 | 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-8374 | 15 Aug 2018 | 2016 Cumulative Update 10; 2016 Cumulative Update 9 | 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-8302 | 15 Aug 2018 | 2010 Service Pack 3 Update Rollup 23; 2013 Cumulative Update 20; 2013 Cumulative Update 21; 2016 Cumulative Update 10; 2016 Cumulative Update 9 | 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-8159 | 9 May 2018 | 2013 Cumulative Update 19; 2013 Cumulative Update 20; 2016 Cumulative Update 8; 2016 Cumulative Update 9 | 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-8154 | 9 May 2018 | 2010 Service Pack 3 Update Rollup 21; 2013 Cumulative Update 19; 2013 Cumulative Update 20; 2013 Service Pack 1; 2016 Cumulative Update 8; 2016 Cumulative Update 9 | 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-8153 | 9 May 2018 | 2016 Cumulative Update 8; 2016 Cumulative Update 9 | 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-8152 | 9 May 2018 | 2016 Cumulative Update 8; 2016 Cumulative Update 9 | 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-8151 | 9 May 2018 | 2010 Service Pack 3 Update Rollup 21; 2013 Cumulative Update 19; 2013 Cumulative Update 20; 2013 Service Pack 1; 2016 Cumulative Update 8; 2016 Cumulative Update 9 | 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-2017-11932 | 12 Dec 2017 | Microsoft Exchange Server 2016 CU5 and Microsoft Exchange Server 2016 CU5 | 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-2017-11761 | 13 Sep 2017 | Microsoft Exchange Server 2013 and Microsoft Exchange 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.