CVE-2020-1065
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 2.24 % · percentile 83.24 % · scored 20 Nov 2026.
Saved 20 Nov 2026 15:48:10 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. The security update addresses the vulnerability by modifying how the ChakraCore scripting engine handles objects in memory.
Read the publisher's advisoryA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. The security update addresses the vulnerability by modifying how the ChakraCore scripting engine handles objects in memory.
Read the publisher's advisoryA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. The security update addresses the vulnerability by modifying how the ChakraCore scripting engine handles objects in memory.
Read the publisher's advisoryA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 2.24 % · percentile 83.24 % · scored 20 Nov 2026.
Saved 20 Nov 2026 15:48:10 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2020-1065 · 20 Nov 2026 15:48:10 UTC
CVE-2020-1065 · 19 Nov 2026 16:46:59 UTC
CVE-2020-1065 · 18 Nov 2026 15:46:44 UTC
CVE-2020-1065 · 17 Nov 2026 15:26:11 UTC
CVE-2020-1065 · 17 Nov 2026 02:39:16 UTC
CVE-2020-1065 · 15 Nov 2026 14:45:34 UTC
CVE-2020-1065 · 14 Nov 2026 16:37:01 UTC
CVE-2020-1065 · 13 Nov 2026 19:59:34 UTC
CVE-2020-1065 · 12 Nov 2026 18:18:51 UTC
CVE-2020-1065 · 10 Nov 2026 20:24:10 UTC
CVE-2020-1065 · 09 Nov 2026 21:04:24 UTC
CVE-2020-1065 · 08 Nov 2026 15:12:21 UTC
CVE-2020-1065 · 07 Nov 2026 16:07:52 UTC
CVE-2020-1065 · 06 Nov 2026 19:10:17 UTC
CVE-2020-1065 · 05 Nov 2026 22:49:22 UTC
CVE-2020-1065 · 05 Nov 2026 02:54:06 UTC
CVE-2020-1065 · 03 Nov 2026 16:59:18 UTC
CVE-2020-1065 · 02 Nov 2026 23:59:04 UTC
CVE-2020-1065 · 01 Nov 2026 23:58:58 UTC
CVE-2020-1065 · 01 Nov 2026 03:04:52 UTC
CVE-2020-1065 · 31 Oct 2026 01:52:30 UTC
CVE-2020-1065 · 29 Oct 2026 18:29:26 UTC
CVE-2020-1065 · 28 Oct 2026 19:55:37 UTC
CVE-2020-1065 · 27 Oct 2026 15:46:19 UTC
CVE-2020-1065 · 27 Oct 2026 00:23:05 UTC
CVE-2020-1065 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
euvd · EUVD-2022-3389 · Published
nvd · CVE-2020-1065 · Published
cve-program · CVE-2020-1065 · Published