CVE-2016-7190

HIGHNVD 7.58.5▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.5 because EPSS predicts 67% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Weaponized
8.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 67%CVSS: 7.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fixed version is listed under Patch Availability — apply it.

The Chakra JavaScript 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-3386, CVE-2016-3389, and CVE-2016-7194.

CVSS v3
7.5
EG Score
8.5HIGHhigh confidence
EG Risk
70
EG Risk 70/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
Severity85% × 45%
Exploitation67% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fixed version is listed under Patch Availability. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
67%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fixed version is listed under Patch Availability. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

October 14, 2016

Last Modified

June 17, 2026

References (6)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
nugetMicrosoft.ChakraCore—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 through 1.2.1: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 22× 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 106 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-40602✓ verified
    First seen Oct 20, 2016

    Microsoft Edge - 'Array.map' Heap Overflow (MS16-119)

    Open source ↗
  • GitHub PoC0xcl/cve-2016-7190
    First seen Feb 13, 2018

    ChakraCore exploitation techniques

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2016-7190?
CVE-2016-7190 is a high vulnerability published on October 14, 2016. The Chakra JavaScript 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-3386, CVE-2016-3389, and…
When was CVE-2016-7190 disclosed?
CVE-2016-7190 was first published on October 14, 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-7190 actively exploited?
CVE-2016-7190 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 67% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-7190?
CVE-2016-7190 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5 (HIGH).
How do I remediate CVE-2016-7190?
A fixed version for CVE-2016-7190 is listed under Patch Availability on this page: update to the version listed for your package.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2016-7190?

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

Book a Demo →Browse All CVEs