A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripti…

published 2019-03-05 7y ago modified 2026-06-17 4mo ago also EUVD-2019-1416

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

A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0590, CVE-2019-0591, CVE-2019-0593, CVE-2019-0605, CVE-2019-0607, CVE-2019-0610, CVE-2019-0640, CVE-2019-0642, CVE-2019-0644, CVE-2019-0651, CVE-2019-0652.

Patch / fix

fixed in 1 links 1

microsoft chakracore 1.11.6

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0655 advisory

Is CVE-2019-0655 in your stack? 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.70% 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

Affected products

Microsoft Microsoft Edge
Microsoft ChakraCore

Classification

Weakness

CWE-787 Out-of-bounds Write

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2019-0655
patch, vendor-advisory
securityfocus.com /bid/106912
vdb-entry, third-party-advisory

Sources

CVE List CVE-2019-0655
NVD CVE-2019-0655

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.