NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
CRITICAL severity

CVE-2017-8658 — Microsoft.ChakraCore

CRITICALFix: chakra-core/ChakraCore#3509

CVE-2017-8658 is a critical-severity (CVSS 9.8) Buffer Overflow vulnerability in Microsoft.ChakraCore. EPSS puts its 30-day exploitation probability at 20.1% (97th percentile). A fix is available for Microsoft.ChakraCore — see the affected versions and patch details below.

ChakraCore RCE Vulnerability

Also known asGHSA-8v2h-4jpm-3wfm
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
20.1%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
15.3%23.8%32.3%40.8%36.0%20.1%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
.NETMicrosoft.ChakraCore

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

A remote code execution vulnerability exists in the way that the Chakra JavaScript engine renders when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability".

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.ChakraCoreall versions1.6.1dotnet add package Microsoft.ChakraCore --version 1.6.1

Affected Products

1 product · 1 configurations
Application
chakracoremicrosoft
≤ 1.7.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.ChakraCore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.ChakraCore to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8658 is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

A remote code execution vulnerability exists in the way that the Chakra JavaScript engine renders when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability".
O3 Security · Impact-Aware SCA

Is CVE-2017-8658 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-8658: Microsoft.ChakraCore RCE — Fixed in 1.6.1