ChakraCore RCE Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2018-8511: 14.23% estimated exploitation activity in the next 30 days; percentile 96.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8503, CVE-2018-8505, CVE-2018-8510, CVE-2018-8513.

Published by the source

13 May 2022, 01:20 UTC

Last modified by the source

14 Oct 2023, 05:03 UTC

Source last checked

26 Oct 2026, 16:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3mv8-x3jj-3j7m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-8511

Advisory: ChakraCore RCE Vulnerability
IDs: CVE-2018-8511, GHSA-3mv8-x3jj-3j7m
Record: https://patchnext.com/advisories/cve-2018-8511 (revision 1, source checked 26 Oct 2026, 16:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.chakracore 1.11.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.chakracore: affected < 1.11.2; fixed in 1.11.2

## Suggested inspection (read-only)
- NuGet microsoft.chakracore: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.chakracore.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3mv8-x3jj-3j7m (GitHub-reviewed advisory GHSA-3mv8-x3jj-3j7m lists affected ranges: NuGet microsoft.chakracore >=0 <1.11.2)

Commands are suggestions: review each one before running it.