CVE-2016-7200

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 82%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
9.0(high)
EPSS
99.6%
KEV
⚠ Exploited

Published

November 10, 2016

Last Modified

April 22, 2026

Advisory Details (5)

Auto-updated May 2, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic
http://www.securityfocus.com/bid/93968
generic🟡 PoC Available

Microsoft Edge (Windows 10) - 'chakra.dll' Information Leak / Type Confusion Remote Code Execution - Windows remote Exploit

https://www.exploit-db.com/exploits/40990/
generic🟡 PoC Available

Microsoft Edge - 'Array.filter' Information Leak - Windows dos Exploit

https://www.exploit-db.com/exploits/40785/
generic🟡 PoC Available

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-11
generic

Microsoft Security Bulletin MS16-129 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-129

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Microsoft.ChakraCore1.2.0, 1.2.11.2.2—

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 46× in last 7d / 200× 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 370 total refreshes for this CVE.

  1. 2026-07-22 17:52 UTCEG score recompute
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-22 09:29 UTCVendor advisory
  4. 2026-07-22 05:18 UTCVendor advisory
  5. 2026-07-22 01:02 UTCVendor advisory
  6. 2026-07-21 18:45 UTCEG score recompute
  7. 2026-07-21 18:45 UTCVendor advisory
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-21 14:37 UTCCISA KEV update
  11. 2026-07-21 14:33 UTCVendor advisory
  12. 2026-07-21 10:22 UTCVendor advisory
  13. 2026-07-21 06:11 UTCVendor advisory
  14. 2026-07-21 01:59 UTCVendor advisory
  15. 2026-07-20 21:48 UTCVendor advisory
  16. 2026-07-20 17:37 UTCEG score recompute
  17. 2026-07-20 17:37 UTCVendor advisory
  18. 2026-07-20 17:04 UTCEPSS rescore
  19. 2026-07-20 09:15 UTCVendor advisory
  20. 2026-07-20 05:04 UTCVendor advisory
  21. 2026-07-20 00:52 UTCVendor advisory
  22. 2026-07-19 20:41 UTCVendor advisory
  23. 2026-07-19 16:29 UTCVendor advisory
  24. 2026-07-19 12:17 UTCVendor advisory
  25. 2026-07-19 08:04 UTCVendor advisory
Show 75 more
  1. 2026-07-19 03:52 UTCVendor advisory
  2. 2026-07-18 19:29 UTCVendor advisory
  3. 2026-07-18 15:18 UTCVendor advisory
  4. 2026-07-18 11:07 UTCVendor advisory
  5. 2026-07-18 06:56 UTCVendor advisory
  6. 2026-07-18 02:45 UTCVendor advisory
  7. 2026-07-17 22:34 UTCVendor advisory
  8. 2026-07-17 18:23 UTCVendor advisory
  9. 2026-07-17 14:12 UTCVendor advisory
  10. 2026-07-17 10:01 UTCEG score recompute
  11. 2026-07-17 10:01 UTCVendor advisory
  12. 2026-07-17 05:50 UTCVendor advisory
  13. 2026-07-17 01:39 UTCVendor advisory
  14. 2026-07-16 21:27 UTCVendor advisory
  15. 2026-07-16 17:16 UTCVendor advisory
  16. 2026-07-16 17:04 UTCCISA KEV update
  17. 2026-07-16 13:04 UTCVendor advisory
  18. 2026-07-16 08:53 UTCVendor advisory
  19. 2026-07-16 04:42 UTCVendor advisory
  20. 2026-07-16 00:31 UTCVendor advisory
  21. 2026-07-15 20:20 UTCVendor advisory
  22. 2026-07-15 16:54 UTCEPSS rescore
  23. 2026-07-15 16:54 UTCEPSS rescore
  24. 2026-07-15 16:49 UTCCISA KEV update
  25. 2026-07-15 16:09 UTCVendor advisory
  26. 2026-07-15 15:04 UTCCISA KEV update
  27. 2026-07-15 11:58 UTCVendor advisory
  28. 2026-07-15 07:47 UTCVendor advisory
  29. 2026-07-15 03:36 UTCVendor advisory
  30. 2026-07-15 01:56 UTCEPSS rescore
  31. 2026-07-14 23:25 UTCVendor advisory
  32. 2026-07-14 19:14 UTCVendor advisory
  33. 2026-07-14 18:05 UTCCISA KEV update
  34. 2026-07-14 15:03 UTCVendor advisory
  35. 2026-07-14 10:51 UTCVendor advisory
  36. 2026-07-14 06:39 UTCVendor advisory
  37. 2026-07-14 02:26 UTCVendor advisory
  38. 2026-07-13 17:07 UTCCISA KEV update
  39. 2026-07-13 05:31 UTCVendor advisory
  40. 2026-07-13 01:20 UTCVendor advisory
  41. 2026-07-12 21:08 UTCVendor advisory
  42. 2026-07-12 16:56 UTCVendor advisory
  43. 2026-07-12 12:44 UTCVendor advisory
  44. 2026-07-12 08:32 UTCVendor advisory
  45. 2026-07-12 05:43 UTCEPSS rescore
  46. 2026-07-12 05:43 UTCEPSS rescore
  47. 2026-07-12 04:21 UTCVendor advisory
  48. 2026-07-12 00:10 UTCVendor advisory
  49. 2026-07-11 19:57 UTCVendor advisory
  50. 2026-07-11 15:46 UTCVendor advisory
  51. 2026-07-11 11:35 UTCVendor advisory
  52. 2026-07-11 07:24 UTCVendor advisory
  53. 2026-07-11 03:12 UTCVendor advisory
  54. 2026-07-10 23:01 UTCVendor advisory
  55. 2026-07-10 18:49 UTCVendor advisory
  56. 2026-07-10 17:52 UTCCISA KEV update
  57. 2026-07-10 14:39 UTCVendor advisory
  58. 2026-07-10 10:27 UTCVendor advisory
  59. 2026-07-10 06:15 UTCVendor advisory
  60. 2026-07-10 02:01 UTCVendor advisory
  61. 2026-07-09 21:49 UTCVendor advisory
  62. 2026-07-09 19:06 UTCEPSS rescore
  63. 2026-07-09 17:38 UTCVendor advisory
  64. 2026-07-09 13:26 UTCVendor advisory
  65. 2026-07-09 09:14 UTCVendor advisory
  66. 2026-07-09 05:02 UTCVendor advisory
  67. 2026-07-09 00:51 UTCVendor advisory
  68. 2026-07-08 20:37 UTCVendor advisory
  69. 2026-07-08 16:25 UTCVendor advisory
  70. 2026-07-08 12:15 UTCVendor advisory
  71. 2026-07-08 08:01 UTCVendor advisory
  72. 2026-07-08 03:50 UTCVendor advisory
  73. 2026-07-07 23:39 UTCVendor advisory
  74. 2026-07-07 19:28 UTCVendor advisory
  75. 2026-07-07 19:01 UTCCISA KEV update

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-40990
    First seen Jan 5, 2017

    Microsoft Edge (Windows 10) - 'chakra.dll' Information Leak / Type Confusion Remote Code Execution

    Open source ↗
  • GitHub PoCtheori-io/chakra-2016-11
    First seen Jan 4, 2017

    Proof-of-Concept exploit for Edge bugs (CVE-2016-7200 & CVE-2016-7201)

    Open source ↗
  • Exploit-DBEDB-40785✓ verified
    First seen Nov 18, 2016

    Microsoft Edge - 'Array.filter' Information Leak

    Open source ↗

Related CVEs(same vendor)

Frequently asked(6)

What is CVE-2016-7200?
CVE-2016-7200 is a high vulnerability published on November 10, 2016. 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,…
When was CVE-2016-7200 disclosed?
CVE-2016-7200 was first published in the National Vulnerability Database on November 10, 2016, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-7200 actively exploited?
Yes. CISA added CVE-2016-7200 to the Known Exploited Vulnerabilities catalog on March 28, 2022, affecting Microsoft Edge. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2016-7200?
CVE-2016-7200 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2016-7200?
CVE-2016-7200 affects Microsoft Edge. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2016-7200?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-7200, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-7200

Explore →

Is Your Infrastructure Affected by CVE-2016-7200?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs