CVE-2018-0776 in the critical feed json
Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the cont…
published 2018-01-04 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-1584
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 78.4%
- EPSS 78.4% chance of exploitation in 30 days, percentile 99.5%
- public exploits
- 1
- Exploit-DB
Summary
Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0758, CVE-2018-0762, CVE-2018-0768, CVE-2018-0769, CVE-2018-0770, CVE-2018-0772, CVE-2018-0773, CVE-2018-0774, CVE-2018-0775, CVE-2018-0777, CVE-2018-0778, and CVE-2018-0781.
Patch / fix
- microsoft chakracore 1.7.6
Timeline
- Published
- First public exploit (EDB-43723)
Exploit prediction
78.43% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-43723 Microsoft Edge Chakra JIT - Stack-to-Heap Copy dos, 2018-01-17
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 Corporation Microsoft Edge
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0776
patch, vendor-advisory
-
exploit-db.com
/exploits/43723/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1040100
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/102401
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0776
- NVD CVE-2018-0776
Fencer Vulns 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.