The Chakra JavaScript scripting engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," a different vulnerability than CVE-2016-7201, CVE-2016-7202, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.
CVE-2016-7200
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 82%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
November 10, 2016
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated May 2, 2026Microsoft Edge (Windows 10) - 'chakra.dll' Information Leak / Type Confusion Remote Code Execution - Windows remote Exploit
https://www.exploit-db.com/exploits/40990/Microsoft Edge - 'Array.filter' Information Leak - Windows dos Exploit
https://www.exploit-db.com/exploits/40785/GitHub - theori-io/chakra-2016-11: Proof-of-Concept exploit for Edge bugs (CVE-2016-7200 & CVE-2016-7201) · GitHub
https://github.com/theori-io/chakra-2016-11Microsoft Security Bulletin MS16-129 - Critical | Microsoft Learn
https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-129Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| Microsoft.ChakraCore | 1.2.0, 1.2.1 | 1.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 48× in last 7d / 184× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 570 total refreshes for this CVE.
- 2026-08-26 04:24 UTCVendor advisory
- 2026-08-26 00:12 UTCVendor advisory
- 2026-08-25 19:58 UTCVendor advisory
- 2026-08-25 15:47 UTCEG score recompute
- 2026-08-25 15:47 UTCVendor advisory
- 2026-08-25 13:44 UTCEPSS rescore
- 2026-08-25 11:36 UTCVendor advisory
- 2026-08-25 07:25 UTCVendor advisory
- 2026-08-25 03:14 UTCVendor advisory
- 2026-08-24 23:03 UTCVendor advisory
- 2026-08-24 18:52 UTCVendor advisory
- 2026-08-24 18:52 UTCCISA KEV update
- 2026-08-24 14:41 UTCEG score recompute
- 2026-08-24 14:41 UTCVendor advisory
- 2026-08-24 10:30 UTCEG score recompute
- 2026-08-24 10:30 UTCVendor advisory
- 2026-08-24 06:18 UTCVendor advisory
- 2026-08-24 02:07 UTCVendor advisory
- 2026-08-23 21:52 UTCVendor advisory
- 2026-08-23 17:41 UTCVendor advisory
- 2026-08-23 13:30 UTCVendor advisory
- 2026-08-23 09:19 UTCVendor advisory
- 2026-08-23 05:08 UTCVendor advisory
- 2026-08-23 00:57 UTCEG score recompute
- 2026-08-23 00:57 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-22 20:46 UTCVendor advisory
- 2026-08-22 16:35 UTCVendor advisory
- 2026-08-22 12:24 UTCVendor advisory
- 2026-08-22 08:13 UTCVendor advisory
- 2026-08-22 04:02 UTCVendor advisory
- 2026-08-21 23:51 UTCVendor advisory
- 2026-08-21 16:49 UTCCISA KEV update
- 2026-08-21 11:18 UTCVendor advisory
- 2026-08-21 07:05 UTCVendor advisory
- 2026-08-21 02:54 UTCEG score recompute
- 2026-08-21 02:54 UTCVendor advisory
- 2026-08-20 22:42 UTCVendor advisory
- 2026-08-20 18:31 UTCVendor advisory
- 2026-08-20 17:06 UTCCISA KEV update
- 2026-08-20 14:20 UTCVendor advisory
- 2026-08-20 10:09 UTCVendor advisory
- 2026-08-19 21:35 UTCVendor advisory
- 2026-08-19 17:33 UTCCISA KEV update
- 2026-08-19 17:24 UTCEG score recompute
- 2026-08-19 17:24 UTCVendor advisory
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-19 13:12 UTCVendor advisory
- 2026-08-19 09:02 UTCVendor advisory
- 2026-08-19 04:48 UTCVendor advisory
- 2026-08-19 00:37 UTCVendor advisory
- 2026-08-18 20:27 UTCVendor advisory
- 2026-08-18 16:58 UTCCISA KEV update
- 2026-08-18 16:16 UTCVendor advisory
- 2026-08-18 12:04 UTCVendor advisory
- 2026-08-18 03:36 UTCVendor advisory
- 2026-08-17 23:23 UTCVendor advisory
- 2026-08-17 19:11 UTCVendor advisory
- 2026-08-17 15:00 UTCVendor advisory
- 2026-08-17 13:56 UTCCISA KEV update
- 2026-08-17 10:49 UTCVendor advisory
- 2026-08-17 06:38 UTCVendor advisory
- 2026-08-17 02:28 UTCVendor advisory
- 2026-08-16 22:17 UTCVendor advisory
- 2026-08-16 18:06 UTCVendor advisory
- 2026-08-16 13:55 UTCVendor advisory
- 2026-08-16 09:44 UTCVendor advisory
- 2026-08-16 05:32 UTCEG score recompute
- 2026-08-16 05:32 UTCVendor advisory
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-16 01:21 UTCVendor advisory
- 2026-08-15 21:10 UTCVendor advisory
- 2026-08-15 16:59 UTCVendor advisory
- 2026-08-15 12:48 UTCVendor advisory
- 2026-08-15 08:37 UTCVendor advisory
- 2026-08-15 04:26 UTCVendor advisory
- 2026-08-15 00:15 UTCVendor advisory
- 2026-08-14 20:04 UTCVendor advisory
- 2026-08-14 15:53 UTCVendor advisory
- 2026-08-14 11:42 UTCVendor advisory
- 2026-08-14 03:20 UTCVendor advisory
- 2026-08-13 23:09 UTCVendor advisory
- 2026-08-13 18:58 UTCVendor advisory
- 2026-08-13 14:47 UTCVendor advisory
- 2026-08-13 10:36 UTCVendor advisory
- 2026-08-13 06:25 UTCVendor advisory
- 2026-08-12 17:53 UTCEG score recompute
- 2026-08-12 17:53 UTCVendor advisory
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-12 13:42 UTCVendor advisory
- 2026-08-12 09:31 UTCVendor advisory
- 2026-08-12 05:20 UTCVendor advisory
- 2026-08-12 01:09 UTCVendor advisory
- 2026-08-11 20:58 UTCVendor advisory
- 2026-08-11 19:32 UTCCISA KEV update
- 2026-08-11 16:47 UTCVendor advisory
- 2026-08-11 12:36 UTCVendor advisory
- 2026-08-11 08:25 UTCVendor advisory
- 2026-08-11 04:14 UTCVendor advisory
- 2026-08-11 00:03 UTCVendor advisory
- 2026-08-10 15:41 UTCEG score recompute
Publicly available exploits
(3 references)Working exploit code is in the public domain (1 GitHub PoC) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-40990First seen Jan 5, 2017
Microsoft Edge (Windows 10) - 'chakra.dll' Information Leak / Type Confusion Remote Code Execution
Open source ↗ - GitHub PoCtheori-io/chakra-2016-11First seen Jan 4, 2017
Proof-of-Concept exploit for Edge bugs (CVE-2016-7200 & CVE-2016-7201)
Open source ↗ - Exploit-DBEDB-40785✓ verifiedFirst seen Nov 18, 2016
Microsoft Edge - 'Array.filter' Information Leak
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-787
Frequently asked(6)
What is CVE-2016-7200?
When was CVE-2016-7200 disclosed?
Is CVE-2016-7200 actively exploited?
What is the CVSS score of CVE-2016-7200?
Which products are affected by CVE-2016-7200?
How do I remediate CVE-2016-7200?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-7200
Is Your Infrastructure Affected by CVE-2016-7200?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.