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

CVE-2018-0818 — Microsoft.ChakraCore

HIGHFix: chakra-core/ChakraCore#4427

CVE-2018-0818 is a high-severity (CVSS 7.5) remote code execution vulnerability in Microsoft.ChakraCore. A fix is available for Microsoft.ChakraCore — see the affected versions and patch details below.

ChakraCore RCE Vulnerability

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk
0.00%11.4%22.9%34.3%27.3%3.7%May 26Sep 26Nov 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

Microsoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka "Scripting Engine Security Feature Bypass".

Affected Packages

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

Affected Products

1 product · 1 configurations
Application
chakracoremicrosoft
all

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.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-0818 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Microsoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka "Scripting Engine Security Feature Bypass".
O3 Security · Impact-Aware SCA

Is CVE-2018-0818 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-0818: Microsoft.ChakraCore RCE — Fixed in 1.8.0