# Type confusion in Microsoft Internet Explorer 11 and others CVE record · `CVE-2019-0752` - **Identifiers:** `CVE-2019-0752` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** Yes: KEV, CVSS 7+ and EPSS - **CNA:** microsoft - **Weakness (CWE):** [CWE-843](https://cwe.mitre.org/data/definitions/843.html) - **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) - **Technologies:** [Microsoft Internet Explorer 11](https://agentprime.io/advisories/technology/microsoft-internet-explorer-11.md) · [Microsoft Internet Explorer 10](https://agentprime.io/advisories/technology/microsoft-internet-explorer-10.md) - **Published:** 9 Apr 2019 - **Updated:** 12 Aug 2026 - **Reviewed by a person:** No Published by the CVE Program (CNA: microsoft) at 9 Apr 2019, 20:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. ## Critical Critical, because: - In CISA’s KEV catalogue since 15 Feb 2022: it is known to be exploited. - CVSS score 7.5 (7.0 or more) and EPSS 0.82 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected products, as the CNA wrote them - Vendor: Microsoft. Product: Internet Explorer 11. - affected: `Windows 7 for 32-bit Systems Service Pack 1` - affected: `Windows 7 for x64-based Systems Service Pack 1` - affected: `Windows Server 2008 R2 for x64-based Systems Service Pack 1` - affected: `Windows 8.1 for 32-bit systems` - affected: `Windows 8.1 for x64-based systems` - affected: `Windows Server 2012 R2` - affected: `Windows RT 8.1` - affected: `Windows 10 for 32-bit Systems` - affected: `Windows 10 for x64-based Systems` - affected: `Windows Server 2016` - affected: `Windows 10 Version 1607 for 32-bit Systems` - affected: `Windows 10 Version 1607 for x64-based Systems` - and 12 more - Vendor: Microsoft. Product: Internet Explorer 10. - affected: `Windows Server 2012` ## Not analysed yet We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter. ## Severity and exploitation - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP) - **CISA KEV:** Listed since 15 Feb 2022: known to be exploited. CISA reports use in ransomware campaigns. - **EPSS:** 0.82, the 99th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline This record came from the full history of the CVE Program, published 9 Apr 2019. New records show when each source confirmed them. ## Sources - [CVE List: CVE-2019-0752](https://www.cve.org/CVERecord?id=CVE-2019-0752) - [NVD: CVE-2019-0752](https://nvd.nist.gov/vuln/detail/CVE-2019-0752) ### References from the CNA - - - Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description. ## Check whether this affects you This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run. - With the agentprime MCP server (), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: - As JSON: - Everything that needs attention now: --- The web page: . Everything for agents: .