← Search results
CVE-LINKED INVENTORY40 SECURITY RECORDS
Microsoft Corporation
ChakraCore, Microsoft Edge
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
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-0939 | 14 Mar 2018 | Microsoft Windows 10 1703 and 1709. | 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-0937 | 14 Mar 2018 | ChakraCore, and Microsoft Windows 10 1703 and 1709. | 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-0936 | 14 Mar 2018 | ChakraCore and Microsoft Windows 10 1709. | 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-0934 | 14 Mar 2018 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2018-0933 | 14 Mar 2018 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2018-0931 | 14 Mar 2018 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2018-0930 | 14 Mar 2018 | ChakraCore and Microsoft Windows 10 1709 | 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-0874 | 14 Mar 2018 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2018-0873 | 14 Mar 2018 | ChakraCore, Microsoft Windows 10 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2018-0872 | 14 Mar 2018 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11918 | 12 Dec 2017 | Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11914 | 12 Dec 2017 | Windows 10 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11911 | 12 Dec 2017 | ChakraCore and Windows 10 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11910 | 12 Dec 2017 | ChakraCore and Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11909 | 12 Dec 2017 | Windows 10 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11908 | 12 Dec 2017 | Windows 10 1709 | 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-11905 | 12 Dec 2017 | Windows 10 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11893 | 12 Dec 2017 | Windows 10 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11889 | 12 Dec 2017 | Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows 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 ↗ |
| CVE-2017-11873 | 15 Nov 2017 | Windows 10 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709. | 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-11871 | 15 Nov 2017 | Windows 10 1703, 1709, and Windows Server, version 1709. | 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-11870 | 15 Nov 2017 | Windows 10 1703, 1709, and Windows Server, version 1709. | 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-11866 | 15 Nov 2017 | Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709. | 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-11862 | 15 Nov 2017 | Windows 10 1709 and Windows Server, version 1709. | 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-11861 | 15 Nov 2017 | Windows 10 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709. | 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-11841 | 15 Nov 2017 | Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709. | 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-11840 | 15 Nov 2017 | Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709. | 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-11836 | 15 Nov 2017 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709. | 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-11821 | 13 Oct 2017 | ChakraCore, Microsoft Windows 10 1703. | 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-11812 | 13 Oct 2017 | ChakraCore and Microsoft Windows 10 1511, 1607, 1703, and Windows 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 ↗ |
| CVE-2017-11809 | 13 Oct 2017 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows 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 ↗ |
| CVE-2017-11808 | 13 Oct 2017 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows 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 ↗ |
| CVE-2017-11807 | 13 Oct 2017 | ChakraCore and Microsoft Windows 10 1703 | 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-11806 | 13 Oct 2017 | ChakraCore and Microsoft Windows 10 1703 | 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-11805 | 13 Oct 2017 | ChakraCore, Microsoft Windows 10 1703. | 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-11804 | 13 Oct 2017 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows 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 ↗ |
| CVE-2017-11802 | 13 Oct 2017 | ChakraCore, Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows 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 ↗ |
| CVE-2017-11799 | 13 Oct 2017 | ChakraCore and Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows 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 ↗ |
| CVE-2017-11796 | 13 Oct 2017 | ChakraCore and Windows 10 1703 | 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-11792 | 13 Oct 2017 | ChakraCore and Microsoft Windows 10 1703 | 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.