CVE-2016-7201

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under NVD CVSS v3. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2022-2363 (ENISA EUVD) · GHSA-4f5g-j7wg-7w8j (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 80%CVSS: 8.8Exploit: Exploit-DB (verified) · other public PoCExposed 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
80
EG Risk 80/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
80% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2016-7201

Published

November 10, 2016

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Nov 9, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page🟡 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/
Web page

Microsoft Edge - 'FillFromPrototypes' Type Confusion - Windows dos Exploit

https://www.exploit-db.com/exploits/40784/
Web page🟡 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
Web page

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(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
nugetMicrosoft.ChakraCore @ 1.2.2 (fixes < 1.2.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 997 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 897 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 01:59 UTCEchelonGraph re-scored
  2. 2026-11-13 01:59 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-12 01:23 UTCEchelonGraph re-scored
  4. 2026-11-12 01:23 UTCVendor advisory
  5. 2026-11-12 01:23 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-11 16:28 UTCEPSS rescoreEPSS 80% · 99th percentile
  7. 2026-11-11 00:47 UTCEchelonGraph re-scored
  8. 2026-11-11 00:47 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-11-10 00:10 UTCEchelonGraph re-scored
  10. 2026-11-10 00:10 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-11-08 23:33 UTCEchelonGraph re-scored
  12. 2026-11-08 23:33 UTCVendor advisory
  13. 2026-11-08 23:33 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-08 16:29 UTCEPSS rescoreEPSS 80% · 99th percentile
  15. 2026-11-07 22:56 UTCEchelonGraph re-scored
  16. 2026-11-07 22:56 UTCVendor advisory
  17. 2026-11-07 22:56 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-06 22:18 UTCEchelonGraph re-scored
  19. 2026-11-06 22:18 UTCVendor advisory
  20. 2026-11-06 22:18 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-05 21:38 UTCEchelonGraph re-scored
  22. 2026-11-05 21:38 UTCVendor advisory
  23. 2026-11-05 21:38 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-11-05 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  25. 2026-11-04 21:02 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-04 21:02 UTCVendor advisory
  2. 2026-11-04 21:02 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-03 20:25 UTCEchelonGraph re-scored
  4. 2026-11-03 20:25 UTCVendor advisory
  5. 2026-11-03 20:25 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-03 16:33 UTCEPSS rescoreEPSS 80% · 99th percentile
  7. 2026-11-02 19:49 UTCEchelonGraph re-scored
  8. 2026-11-02 19:49 UTCVendor advisory
  9. 2026-11-02 19:49 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-01 19:12 UTCEchelonGraph re-scored
  11. 2026-11-01 19:12 UTCVendor advisory
  12. 2026-11-01 19:12 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-11-01 08:46 UTCGHSA enrichmentGHSA-4f5g-j7wg-7w8j · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-01 08:46 UTCEchelonGraph re-scored
  15. 2026-10-31 18:34 UTCEchelonGraph re-scored
  16. 2026-10-31 18:34 UTCVendor advisory
  17. 2026-10-31 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  18. 2026-10-30 17:57 UTCEchelonGraph re-scored
  19. 2026-10-30 17:57 UTCVendor advisory
  20. 2026-10-29 17:21 UTCEchelonGraph re-scored
  21. 2026-10-29 17:21 UTCVendor advisory
  22. 2026-10-29 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  23. 2026-10-28 16:44 UTCEchelonGraph re-scored
  24. 2026-10-27 16:26 UTCEPSS rescoreEPSS 80% · 99th percentile
  25. 2026-10-27 16:05 UTCEchelonGraph re-scored
  26. 2026-10-27 16:05 UTCVendor advisory
  27. 2026-10-26 15:23 UTCEchelonGraph re-scored
  28. 2026-10-25 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  29. 2026-10-25 14:47 UTCEchelonGraph re-scored
  30. 2026-10-25 14:47 UTCVendor advisory
  31. 2026-10-24 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  32. 2026-10-24 14:09 UTCEchelonGraph re-scored
  33. 2026-10-24 14:09 UTCVendor advisory
  34. 2026-10-23 13:33 UTCEchelonGraph re-scored
  35. 2026-10-22 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  36. 2026-10-22 12:56 UTCEchelonGraph re-scored
  37. 2026-10-21 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  38. 2026-10-21 12:19 UTCEchelonGraph re-scored
  39. 2026-10-21 12:19 UTCVendor advisory
  40. 2026-10-20 11:42 UTCEchelonGraph re-scored
  41. 2026-10-19 16:26 UTCEPSS rescoreEPSS 80% · 99th percentile
  42. 2026-10-19 11:06 UTCEchelonGraph re-scored
  43. 2026-10-19 11:06 UTCVendor advisory
  44. 2026-10-18 16:26 UTCEPSS rescoreEPSS 80% · 99th percentile
  45. 2026-10-18 10:28 UTCEchelonGraph re-scored
  46. 2026-10-18 10:28 UTCVendor advisory
  47. 2026-10-17 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  48. 2026-10-17 09:49 UTCEchelonGraph re-scored
  49. 2026-10-16 09:12 UTCEchelonGraph re-scored
  50. 2026-10-15 08:35 UTCEchelonGraph re-scored
  51. 2026-10-14 16:27 UTCEPSS rescoreEPSS 80% · 99th percentile
  52. 2026-10-14 07:56 UTCEchelonGraph re-scored
  53. 2026-10-13 07:18 UTCVendor advisory
  54. 2026-10-12 20:40 UTCEchelonGraph re-scored
  55. 2026-10-12 06:40 UTCVendor advisory
  56. 2026-10-12 02:36 UTCVendor advisory
  57. 2026-10-11 22:31 UTCEchelonGraph re-scored
  58. 2026-10-11 22:31 UTCVendor advisory
  59. 2026-10-11 18:28 UTCEchelonGraph re-scored
  60. 2026-10-11 18:28 UTCVendor advisory
  61. 2026-10-11 14:27 UTCEchelonGraph re-scored
  62. 2026-10-11 14:27 UTCVendor advisory
  63. 2026-10-11 10:26 UTCVendor advisory
  64. 2026-10-11 06:24 UTCVendor advisory
  65. 2026-10-11 02:23 UTCVendor advisory
  66. 2026-10-10 22:18 UTCVendor advisory
  67. 2026-10-10 14:13 UTCVendor advisory
  68. 2026-10-10 10:11 UTCVendor advisory
  69. 2026-10-10 06:06 UTCVendor advisory
  70. 2026-10-10 02:05 UTCVendor advisory
  71. 2026-10-09 22:04 UTCEchelonGraph re-scored
  72. 2026-10-09 22:04 UTCVendor advisory
  73. 2026-10-09 20:01 UTCEPSS rescoreEPSS 80% · 99th percentile
  74. 2026-10-09 18:02 UTCVendor advisory
  75. 2026-10-09 14:00 UTCVendor advisory

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 Exploit-DB entries). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-40784✓ verified
    Published Nov 18, 2016

    Microsoft Edge - 'FillFromPrototypes' Type Confusion

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

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

    Open source ↗

Frequently asked(6)

What is CVE-2016-7201?
CVE-2016-7201 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2016-7201 was made public on November 8, 2016: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on November 10, 2016. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
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.