CVE-2016-7194

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 58%
CISA-KEV: Not listedEPSS: 58%CVSS: 7.5Exploit: NoneExposed: 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-7190.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
99.0%
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 3× in last 7d / 23× 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-09 19:06 UTCEPSS rescore
  2. 2026-07-07 13:42 UTCEPSS rescore
  3. 2026-07-05 02:27 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-27 03:05 UTCEPSS rescore
  8. 2026-06-25 13:47 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-22 14:23 UTCEPSS rescore
  11. 2026-06-21 01:57 UTCEPSS rescore
  12. 2026-06-21 01:57 UTCEPSS rescore
  13. 2026-06-19 19:23 UTCEPSS rescore
  14. 2026-06-19 19:23 UTCEPSS rescore
  15. 2026-06-18 17:50 UTCEPSS rescore
  16. 2026-06-18 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-13 22:57 UTCEPSS rescore
  22. 2026-06-13 22:57 UTCEPSS rescore
  23. 2026-06-12 23:09 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
Show 26 more
  1. 2026-06-06 13:45 UTCEPSS rescore
  2. 2026-06-06 13:45 UTCEPSS rescore
  3. 2026-06-05 22:44 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-05 06:08 UTCEPSS rescore
  6. 2026-06-04 13:10 UTCEPSS rescore
  7. 2026-06-04 13:10 UTCEPSS rescore
  8. 2026-06-01 13:49 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-05-31 22:28 UTCEPSS rescore
  11. 2026-05-31 22:28 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-29 13:41 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-26 07:17 UTCEPSS rescore
  17. 2026-05-24 16:44 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-22 18:18 UTCEG score recompute
  20. 2026-05-22 18:18 UTCGHSA enrichment
  21. 2026-05-20 22:37 UTCEPSS rescore
  22. 2026-05-20 22:37 UTCEPSS rescore
  23. 2026-05-20 22:37 UTCEPSS rescore
  24. 2026-05-18 21:30 UTCEPSS rescore
  25. 2026-05-18 21:30 UTCEPSS rescore
  26. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

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

    Microsoft Edge - 'Function.apply' Information Leak (MS16-119)

    Open source ↗

Frequently asked(5)

What is CVE-2016-7194?
CVE-2016-7194 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-7194 disclosed?
CVE-2016-7194 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-7194 actively exploited?
CVE-2016-7194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-7194?
CVE-2016-7194 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2016-7194?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-7194, 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-7194

Explore →

Is Your Infrastructure Affected by CVE-2016-7194?

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

Start Free Scan →Browse All CVEs