CVE-2018-8459: ChakraCore RCE Vulnerability in Microsoft.ChakraCore

Microsoft.ChakraCore Updated 02 Oct 2025

Summary

13/05/2022
Yes i
High
7.5

CVE-2018-8459: ChakraCore RCE Vulnerability. Affects Microsoft.ChakraCore versions < 1.11.1. Fixed in 1.11.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Microsoft.ChakraCore is a scripting engine used by Microsoft Edge. It provides support for executing JavaScript code and is an integral part of the Edge browser. ChakraCore is also available as a standalone package for developers to embed in their applications. This vulnerability affects versions prior to 1.11.1 of the Microsoft.ChakraCore package.

Vulnerability Detail

A remote code execution vulnerability, known as CVE-2018-8459 or "Scripting Engine Memory Corruption Vulnerability," has been discovered in ChakraCore. This vulnerability arises from the mishandling of objects in memory by the ChakraCore scripting engine. It affects both Microsoft Edge and ChakraCore. Exploitation of this vulnerability could allow an attacker to execute arbitrary code on a target system. The severity of this vulnerability is rated as HIGH with a CVSS score of 7.5.

How To Fix

Latest published version: 1.11.24 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.11.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update to the fixed version of the Microsoft.ChakraCore package to ensure the security of the system.

Conclusion

The CVE-2018-8459 vulnerability in Microsoft.ChakraCore poses a significant risk as it allows remote code execution. To mitigate this vulnerability, it is crucial to update the Microsoft.ChakraCore package to version 1.11.1 or later. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Microsoft.ChakraCore →

Share this vulnerability

FAQ

Microsoft.ChakraCore is a scripting engine used by Microsoft Edge and can be embedded in other applications.

This vulnerability allows remote code execution, which means an attacker could execute arbitrary code on a target system.

To fix this vulnerability, update the Microsoft.ChakraCore package to version 1.11.1 or later.

No, there is no known workaround. Updating to the fixed version is the recommended solution.

The severity of this vulnerability is rated as HIGH with a CVSS score of 7.5.

Related vulnerabilities

Recent vulnerabilities recorded for Microsoft.ChakraCore.

How To Fix

Latest published version: 1.11.24 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.11.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback