Chakra Core vulnerable to privilege escalation due to type confusion

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-2017-11862: 7.91% estimated exploitation activity in the next 30 days; percentile 94.73 (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.

ChakraCore and Microsoft Edge in Windows 10 1709 and Windows Server, version 1709 allows an attacker to gain the same user rights as the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". Individual Export in module exports was not taking care of destructuring nodes, leading to type confusion. This was fixed by adding support for walking those nodes. This CVE ID is unique from CVE-2017-11836, CVE-2017-11837, CVE-2017-11838, CVE-2017-11839, CVE-2017-11840, CVE-2017-11841, CVE-2017-11843, CVE-2017-11846, CVE-2017-11858, CVE-2017-11859, CVE-2017-11861, CVE-2017-11866, CVE-2017-11869, CVE-2017-11870, CVE-2017-11871, and CVE-2017-11873.

Published by the source

17 May 2022, 00:19 UTC

Last modified by the source

10 Oct 2023, 16:20 UTC

Source last checked

26 Oct 2026, 16:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pcr8-75v3-w9pf

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

# Patch Next advisory brief: CVE-2017-11862

Advisory: Chakra Core vulnerable to privilege escalation due to type confusion
IDs: CVE-2017-11862, GHSA-pcr8-75v3-w9pf
Record: https://patchnext.com/advisories/cve-2017-11862 (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.7.4. A vendor fix does not mean a deployment is fixed.

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

## 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-pcr8-75v3-w9pf (GitHub-reviewed advisory GHSA-pcr8-75v3-w9pf lists affected ranges: NuGet microsoft.chakracore >=0 <1.7.4)

Commands are suggestions: review each one before running it.