Skip to content
Fencer Intel
high 7.5

CVE-2019-0639 in the critical feed json

High severity vulnerability that affects Microsoft.ChakraCore

published 7y ago modified 4mo ago also GHSA-6jf5-rmhv-38cw , EUVD-2019-0404

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.0%
EPSS 12.0% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.

Patch / fix

  • nuget Microsoft.ChakraCore 1.11.7

Is CVE-2019-0639 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

12.05% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
nuget Microsoft.ChakraCore
<1.11.7
1.11.7

Affected products

  • Microsoft Microsoft Edge
  • Microsoft ChakraCore

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.