← Search results
CVE-LINKED INVENTORY20 SECURITY RECORDS
Microsoft Corporation
Microsoft Malware Protection Engine
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-2026-69414 | 14 Aug 2026 | Microsoft Malware Protection Engine: 1.1.0.0 < 1.1.26080.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-55012 | 14 Jul 2026 | Microsoft Malware Protection Engine: 1.1.0.0 < 1.1.26060.3008 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-55011 | 14 Jul 2026 | Microsoft Malware Protection Engine: 1.1.0.0 < 1.1.26060.3008 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50656 | 16 Jun 2026 | Microsoft Malware Protection Engine: 1.1.0.0 < 1.1.26060.3008 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-45584 | 20 May 2026 | 1.1.0.0 < 1.1.26040.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-33156 | 11 Jul 2023 | 1.1.0.0 < 1.1.23050.3 | 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-2023-24860 | 11 Apr 2023 | 1.1.0.0 < 1.1.20200.4 | 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-2023-23389 | 14 Mar 2023 | 1.1.0.0 < 1.1.20000.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-2022-37971 | 11 Oct 2022 | 1.1.0.0 < 1.1.19700.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-2022-24548 | 15 Apr 2022 | 1.1.0.0 < 1.1.19100.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-42298 | 10 Nov 2021 | 1.1.0.0 < 1.1.18700.3 | 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-2021-34471 | 12 Aug 2021 | 1.1.0.0 < 1.1.18400.4 | 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-2021-34464 | 16 Jul 2021 | 1.1.0.0 < 1.1.18242.0 | 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-2021-34522 | 14 Jul 2021 | 1.1.0.0 < 1.1.18242.0 | 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-2021-31985 | 8 Jun 2021 | 1.1.0.0 < Version 1.1.18200.3 | 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-2021-31978 | 8 Jun 2021 | 1.1.0.0 < Version 1.1.18200.3 | 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-11940 | 8 Dec 2017 | Microsoft Forefront and Microsoft Defender on Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, 1709 and Windows Server 2016, Windows Server, version 1709, Microsoft Exchange Server 2013 and 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-11937 | 7 Dec 2017 | Microsoft Forefront and Microsoft Defender on Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, 1709 and Windows Server 2016, Windows Server, version 1709, Microsoft Exchange Server 2013 and 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-8558 | 29 Jun 2017 | 32-bit versions only of Microsoft Forefront and Microsoft Defender on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016, Microsoft Exchange Server 2013 and 2016. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-0290 | 9 May 2017 | Microsoft Forefront and Microsoft Defender on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 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 ↗ |
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.