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 (top 0.8% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
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: 0

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

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.5(high)
EG Risk
70(Track)
EG Risk 70/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
67%
EPSS %ILE
99%
KEV
Not listed

Published

October 14, 2016

Last Modified

May 6, 2026

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
Microsoft.ChakraCore1.2.0, 1.2.1——

Data Freshness Timeline

(refreshed 9× in last 7d / 26× 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.

  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-24 14:13 UTCEPSS rescore
  3. 2026-07-23 14:15 UTCEPSS rescore
  4. 2026-07-23 01:24 UTCEG score recompute▲ 1.00
  5. 2026-07-22 22:03 UTCEG score recompute
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-19 14:28 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-16 16:59 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-15 01:56 UTCEPSS rescore
  17. 2026-07-13 06:09 UTCEPSS rescore
  18. 2026-07-11 08:24 UTCEPSS rescore
  19. 2026-07-09 19:06 UTCEPSS rescore
  20. 2026-07-06 16:24 UTCEPSS rescore
  21. 2026-07-06 16:24 UTCEPSS rescore
  22. 2026-07-04 06:28 UTCEPSS rescore
  23. 2026-07-01 15:02 UTCEPSS rescore
  24. 2026-06-30 23:19 UTCEPSS rescore
  25. 2026-06-30 23:19 UTCEPSS rescore
Show 37 more
  1. 2026-06-29 14:03 UTCEPSS rescore
  2. 2026-06-27 03:05 UTCEPSS rescore
  3. 2026-06-25 13:47 UTCEPSS rescore
  4. 2026-06-24 14:02 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-17 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-16 17:50 UTCEPSS rescore
  9. 2026-06-15 17:45 UTCEPSS rescore
  10. 2026-06-13 22:57 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-07 15:22 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-05 22:44 UTCEPSS rescore
  18. 2026-06-05 06:08 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-04 13:10 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-02 20:10 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
  26. 2026-05-29 13:41 UTCEPSS rescore
  27. 2026-05-22 21:15 UTCEPSS rescore
  28. 2026-05-22 18:18 UTCEG score recompute
  29. 2026-05-22 18:18 UTCGHSA enrichment
  30. 2026-05-20 22:37 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 11:21 UTCEPSS rescore
  34. 2026-05-20 11:21 UTCEPSS rescore
  35. 2026-05-18 21:30 UTCEPSS rescore
  36. 2026-05-18 21:30 UTCEPSS rescore
  37. 2026-05-18 21:30 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.

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

    ChakraCore exploitation techniques

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

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

    Open source ↗

Related CVEs(same product)

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 in the National Vulnerability Database on October 14, 2016, with the most recent update on May 6, 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. FIRST EPSS estimates a 67% probability of exploitation in the next 30 days, which ranks it in the top 0.8% of all 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.
How do I remediate CVE-2016-7190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-7190, 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-7190

Explore →

Is Your Infrastructure Affected by CVE-2016-7190?

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

Start Free Scan →Browse All CVEs