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
- 83%
- 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 52× in last 7d / 202× 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 731 total refreshes for this CVE.
- 2026-09-19 07:34 UTCVendor advisory
- 2026-09-19 03:22 UTCVendor advisory
- 2026-09-18 23:11 UTCEG score recompute
- 2026-09-18 23:11 UTCVendor advisory
- 2026-09-18 19:22 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 19:00 UTCVendor advisory
- 2026-09-18 14:49 UTCVendor advisory
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 10:38 UTCVendor advisory
- 2026-09-18 06:27 UTCVendor advisory
- 2026-09-18 02:16 UTCVendor advisory
- 2026-09-17 22:05 UTCEG score recompute
- 2026-09-17 22:05 UTCVendor advisory
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-17 17:53 UTCVendor advisory
- 2026-09-17 13:41 UTCVendor advisory
- 2026-09-17 09:29 UTCVendor advisory
- 2026-09-17 05:18 UTCVendor advisory
- 2026-09-17 01:07 UTCVendor advisory
- 2026-09-16 20:56 UTCVendor advisory
- 2026-09-16 16:44 UTCEG score recompute
- 2026-09-16 16:44 UTCVendor advisory
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 12:29 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-16 08:18 UTCVendor advisory
- 2026-09-16 04:03 UTCVendor advisory
- 2026-09-15 23:50 UTCVendor advisory
- 2026-09-15 19:39 UTCVendor advisory
- 2026-09-15 15:28 UTCVendor advisory
- 2026-09-15 11:17 UTCVendor advisory
- 2026-09-15 07:06 UTCEG score recompute
- 2026-09-15 07:06 UTCVendor advisory
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-14 22:44 UTCVendor advisory
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 18:33 UTCVendor advisory
- 2026-09-14 14:20 UTCVendor advisory
- 2026-09-14 10:09 UTCVendor advisory
- 2026-09-14 05:58 UTCVendor advisory
- 2026-09-14 01:47 UTCVendor advisory
- 2026-09-13 21:36 UTCVendor advisory
- 2026-09-13 17:25 UTCVendor advisory
- 2026-09-13 13:14 UTCVendor advisory
- 2026-09-13 09:02 UTCVendor advisory
- 2026-09-13 04:51 UTCVendor advisory
- 2026-09-13 00:41 UTCVendor advisory
- 2026-09-12 20:30 UTCVendor advisory
- 2026-09-12 16:19 UTCEG score recompute
- 2026-09-12 16:19 UTCVendor advisory
- 2026-09-12 14:55 UTCEPSS rescore
- 2026-09-12 12:07 UTCVendor advisory
- 2026-09-12 07:56 UTCVendor advisory
- 2026-09-12 03:45 UTCVendor advisory
- 2026-09-11 23:34 UTCVendor advisory
- 2026-09-11 19:23 UTCVendor advisory
- 2026-09-11 18:49 UTCCISA KEV update
- 2026-09-11 15:12 UTCVendor advisory
- 2026-09-10 19:28 UTCCISA KEV update
- 2026-09-10 09:55 UTCEG score recompute
- 2026-09-10 09:26 UTCEPSS rescore
- 2026-09-09 21:22 UTCVendor advisory
- 2026-09-09 19:08 UTCCISA KEV update
- 2026-09-09 17:07 UTCVendor advisory
- 2026-09-09 12:56 UTCVendor advisory
- 2026-09-09 08:45 UTCVendor advisory
- 2026-09-09 04:34 UTCVendor advisory
- 2026-09-09 00:23 UTCEG score recompute
- 2026-09-09 00:23 UTCVendor advisory
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 16:00 UTCVendor advisory
- 2026-09-08 11:45 UTCVendor advisory
- 2026-09-08 07:33 UTCVendor advisory
- 2026-09-08 03:21 UTCVendor advisory
- 2026-09-07 23:10 UTCVendor advisory
- 2026-09-07 18:59 UTCVendor advisory
- 2026-09-07 14:48 UTCVendor advisory
- 2026-09-07 10:35 UTCVendor advisory
- 2026-09-07 06:22 UTCVendor advisory
- 2026-09-07 02:08 UTCVendor advisory
- 2026-09-06 21:55 UTCVendor advisory
- 2026-09-06 17:42 UTCEG score recompute
- 2026-09-06 17:42 UTCVendor advisory
- 2026-09-06 13:31 UTCVendor advisory
- 2026-09-06 09:20 UTCVendor advisory
- 2026-09-06 05:09 UTCVendor advisory
- 2026-09-06 00:58 UTCVendor advisory
- 2026-09-05 20:44 UTCVendor advisory
- 2026-09-05 16:33 UTCEG score recompute
- 2026-09-05 16:33 UTCVendor advisory
- 2026-09-05 12:22 UTCVendor advisory
- 2026-09-05 08:07 UTCVendor advisory
- 2026-09-05 03:56 UTCVendor advisory
- 2026-09-04 23:45 UTCVendor advisory
- 2026-09-04 19:34 UTCVendor advisory
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 15:21 UTCVendor advisory
- 2026-09-04 11:10 UTCVendor advisory
- 2026-09-04 06:58 UTCEG score recompute
- 2026-09-04 06:58 UTCVendor advisory
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.