CVE-2016-7201

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: 80%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-7200, 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/94038
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 - 'FillFromPrototypes' Type Confusion - Windows dos Exploit

https://www.exploit-db.com/exploits/40784/
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 91× in last 7d / 367× 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 549 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (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 ↗
  • Exploit-DBEDB-40784✓ verified
    First seen Nov 18, 2016

    Microsoft Edge - 'FillFromPrototypes' Type Confusion

    Open source ↗

Frequently asked(6)

What is CVE-2016-7201?
CVE-2016-7201 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-7200, CVE-2016-7202,…
When was CVE-2016-7201 disclosed?
CVE-2016-7201 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-7201 actively exploited?
Yes. CISA added CVE-2016-7201 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-7201?
CVE-2016-7201 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-7201?
CVE-2016-7201 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-7201?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-7201, 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-7201

Explore →

Is Your Infrastructure Affected by CVE-2016-7201?

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

Start Free Scan →Browse All CVEs