CVE-2016-7201

CRITICALNVD 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 — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 80%CVSS: 8.8Exploit: cisa kev · ssvc active · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

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.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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 computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
80%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 10, 2016

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated May 2, 2026
🔬 Proof of concept available. Patch available.
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

Vendor Advisories for CVE-2016-7201(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.ChakraCore1.2.0, 1.2.1
  • every version up to 1.2.2: fixed in 1.2.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 51× in last 7d / 219× 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 905 total refreshes for this CVE.

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

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-40784✓ verified
    First seen Nov 18, 2016

    Microsoft Edge - 'FillFromPrototypes' Type Confusion

    Open source ↗
  • Exploit-DBEDB-40990
    First seen Jan 5, 2017

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

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(6)

What is CVE-2016-7201?
CVE-2016-7201 is a critical 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 on November 10, 2016, with the most recent update on June 17, 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 attention. A fix is available. Apply it.
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 (CRITICAL).
Which products are affected by CVE-2016-7201?
CVE-2016-7201 affects Microsoft Edge. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2016-7201?
A fix for CVE-2016-7201 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-7201 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs