Internet Explorer 10
Microsoft- Software type
- —
- Catalog vulnerabilities
- 86
Severity across 86 analyzed records
Verify to analyze this security profile
A short verification protects source data and prevents automated AI requests.
en
Severity across 86 analyzed records
A short verification protects source data and prevents automated AI requests.
As of 09/11/2026, within CyStack's analyzed data, Internet Explorer 10 has 0 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Internet Explorer 10 and determine which vulnerabilities affect that version.
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2020-0706CVE-2020-0706 | Exploitation statusNot confirmed | FixNot confirmed | Published02/11/2020 | SeverityUnknown |
CVE-2020-0673CVE-2020-0673 | Exploitation statusNot confirmed | FixNot confirmed | Published02/11/2020 | SeverityUnknown |
CVE-2020-0674CVE-2020-0674 | Exploitation statusKEV | FixNot confirmed | Published02/11/2020 | SeverityHigh |
CVE-2020-0640CVE-2020-0640 | Exploitation statusNot confirmed | FixNot confirmed | Published01/14/2020 | SeverityUnknown |
CVE-2019-1485CVE-2019-1485 | Exploitation statusNot confirmed | FixNot confirmed | Published12/10/2019 | SeverityUnknown |
CVE-2019-1429CVE-2019-1429 | Exploitation statusKEV | FixNot confirmed | Published11/12/2019 | SeverityHigh |
CVE-2019-1390CVE-2019-1390 | Exploitation statusNot confirmed | FixNot confirmed | Published11/12/2019 | SeverityUnknown |
CVE-2019-1371CVE-2019-1371 | Exploitation statusNot confirmed | FixNot confirmed | Published10/10/2019 | SeverityUnknown |
CVE-2019-1357CVE-2019-1357 | Exploitation statusNot confirmed | FixNot confirmed | Published10/10/2019 | SeverityUnknown |
CVE-2019-1238CVE-2019-1238 | Exploitation statusNot confirmed | FixNot confirmed | Published10/10/2019 | SeverityUnknown |
CVE-2019-0608CVE-2019-0608 | Exploitation statusNot confirmed | FixNot confirmed | Published10/10/2019 | SeverityUnknown |
CVE-2019-1367CVE-2019-1367 | Exploitation statusKEV | FixNot confirmed | Published09/23/2019 | SeverityHigh |
CVE-2019-1220CVE-2019-1220 | Exploitation statusNot confirmed | FixNot confirmed | Published09/11/2019 | SeverityUnknown |
CVE-2019-1236CVE-2019-1236 | Exploitation statusNot confirmed | FixNot confirmed | Published09/11/2019 | SeverityUnknown |
CVE-2019-1208CVE-2019-1208 | Exploitation statusNot confirmed | FixNot confirmed | Published09/11/2019 | SeverityUnknown |
CVE-2019-1193Microsoft Browser Memory Corruption Vulnerability | Exploitation statusPublic exploit | FixYes | Published08/14/2019 | SeverityMedium |
CVE-2019-1192Microsoft Browsers Security Feature Bypass Vulnerability | Exploitation statusNot confirmed | FixYes | Published08/14/2019 | SeverityMedium |
CVE-2019-1194Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot known exploited | FixYes | Published08/14/2019 | SeverityHigh |
CVE-2019-1133Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published08/14/2019 | SeverityHigh |
CVE-2019-1104CVE-2019-1104 | Exploitation statusNot confirmed | FixNot confirmed | Published07/29/2019 | SeverityUnknown |
CVE-2019-1063CVE-2019-1063 | Exploitation statusNot confirmed | FixNot confirmed | Published07/15/2019 | SeverityUnknown |
CVE-2019-1004CVE-2019-1004 | Exploitation statusNot confirmed | FixNot confirmed | Published07/15/2019 | SeverityUnknown |
CVE-2019-1059CVE-2019-1059 | Exploitation statusNot confirmed | FixNot confirmed | Published07/15/2019 | SeverityUnknown |
CVE-2019-1081Microsoft Browser Information Disclosure Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityMedium |
CVE-2019-1080Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityHigh |
CVE-2019-1055Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityHigh |
CVE-2019-1038Microsoft Browser Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityHigh |
CVE-2019-1005Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityHigh |
CVE-2019-0988Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityHigh |
CVE-2019-0920Scripting Engine Memory Corruption Vulnerability | Exploitation statusNot confirmed | FixYes | Published06/12/2019 | SeverityMedium |
CVE-2019-0940CVE-2019-0940 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2019 | SeverityUnknown |
CVE-2019-0918CVE-2019-0918 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2019 | SeverityUnknown |
CVE-2019-0930CVE-2019-0930 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2019 | SeverityUnknown |
CVE-2019-0911CVE-2019-0911 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2019 | SeverityUnknown |
CVE-2019-0921CVE-2019-0921 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2019 | SeverityUnknown |
CVE-2019-0884CVE-2019-0884 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2019 | SeverityUnknown |
CVE-2019-0862CVE-2019-0862 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0835CVE-2019-0835 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0753CVE-2019-0753 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0752CVE-2019-0752 | Exploitation statusKEV | FixNot confirmed | Published04/09/2019 | SeverityHigh |
CVE-2019-0764CVE-2019-0764 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0783CVE-2019-0783 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0780CVE-2019-0780 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0761CVE-2019-0761 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0763CVE-2019-0763 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-0746CVE-2019-0746 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2019 | SeverityUnknown |
CVE-2019-0667CVE-2019-0667 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2019 | SeverityUnknown |
CVE-2019-0666CVE-2019-0666 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2019 | SeverityUnknown |
CVE-2019-0665CVE-2019-0665 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2019 | SeverityUnknown |
CVE-2019-0654CVE-2019-0654 | Exploitation statusNot confirmed | FixNot confirmed | Published03/06/2019 | SeverityUnknown |
CVE-2019-0676CVE-2019-0676 | Exploitation statusKEV | FixNot confirmed | Published03/06/2019 | SeverityMedium |
CVE-2019-0541CVE-2019-0541 | Exploitation statusKEV | FixNot confirmed | Published01/08/2019 | SeverityHigh |
CVE-2018-8653CVE-2018-8653 | Exploitation statusKEV | FixNot confirmed | Published12/20/2018 | SeverityHigh |
CVE-2018-8619CVE-2018-8619 | Exploitation statusPublic exploit | FixNot confirmed | Published12/12/2018 | SeverityUnknown |
CVE-2018-8643CVE-2018-8643 | Exploitation statusNot confirmed | FixNot confirmed | Published12/12/2018 | SeverityUnknown |
CVE-2018-8625CVE-2018-8625 | Exploitation statusPublic exploit | FixNot confirmed | Published12/12/2018 | SeverityUnknown |
CVE-2018-8631CVE-2018-8631 | Exploitation statusPublic exploit | FixNot confirmed | Published12/12/2018 | SeverityUnknown |
CVE-2018-8552CVE-2018-8552 | Exploitation statusPublic exploit | FixNot confirmed | Published11/14/2018 | SeverityUnknown |
CVE-2018-8457CVE-2018-8457 | Exploitation statusNot confirmed | FixNot confirmed | Published09/13/2018 | SeverityUnknown |
CVE-2018-8315CVE-2018-8315 | Exploitation statusNot confirmed | FixNot confirmed | Published09/13/2018 | SeverityUnknown |
CVE-2018-8447CVE-2018-8447 | Exploitation statusNot confirmed | FixNot confirmed | Published09/13/2018 | SeverityUnknown |
CVE-2018-8351CVE-2018-8351 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2018 | SeverityUnknown |
CVE-2018-8316CVE-2018-8316 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2018 | SeverityUnknown |
CVE-2018-8371CVE-2018-8371 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2018 | SeverityUnknown |
CVE-2018-8403CVE-2018-8403 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2018 | SeverityUnknown |
CVE-2018-8373CVE-2018-8373 | Exploitation statusKEV | FixNot confirmed | Published08/15/2018 | SeverityHigh |
CVE-2018-8389CVE-2018-8389 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2018 | SeverityUnknown |
CVE-2018-8385CVE-2018-8385 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2018 | SeverityUnknown |
CVE-2018-8287CVE-2018-8287 | Exploitation statusNot confirmed | FixNot confirmed | Published07/11/2018 | SeverityUnknown |
CVE-2018-8242CVE-2018-8242 | Exploitation statusNot confirmed | FixNot confirmed | Published07/11/2018 | SeverityUnknown |
CVE-2018-0949CVE-2018-0949 | Exploitation statusNot confirmed | FixNot confirmed | Published07/11/2018 | SeverityUnknown |
CVE-2018-0978CVE-2018-0978 | Exploitation statusNot confirmed | FixNot confirmed | Published06/14/2018 | SeverityUnknown |
CVE-2018-8267CVE-2018-8267 | Exploitation statusNot confirmed | FixNot confirmed | Published06/14/2018 | SeverityUnknown |
CVE-2018-0954CVE-2018-0954 | Exploitation statusNot confirmed | FixNot confirmed | Published05/09/2018 | SeverityUnknown |
CVE-2018-8145CVE-2018-8145 | Exploitation statusPublic exploit | FixNot confirmed | Published05/09/2018 | SeverityUnknown |
CVE-2018-0955CVE-2018-0955 | Exploitation statusNot confirmed | FixNot confirmed | Published05/09/2018 | SeverityUnknown |
CVE-2018-8118CVE-2018-8118 | Exploitation statusNot confirmed | FixNot confirmed | Published04/19/2018 | SeverityUnknown |
CVE-2018-0989CVE-2018-0989 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-0987CVE-2018-0987 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-0988CVE-2018-0988 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-0991CVE-2018-0991 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-1001CVE-2018-1001 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-1020CVE-2018-1020 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-0981CVE-2018-0981 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-1000CVE-2018-1000 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CVE-2018-0996CVE-2018-0996 | Exploitation statusNot confirmed | FixNot confirmed | Published04/12/2018 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan