CVE-2016-0024

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 32.4%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 18%CVSS: 8.8Exploit: 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 via unspecified vectors, aka "Scripting Engine Memory Corruption Vulnerability."

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
96.8%
KEV
Not listed

Published

January 13, 2016

Last Modified

May 6, 2026

Advisory Details (2)

Auto-updated May 9, 2026
No patch confirmed yet.

Frequently asked(5)

What is CVE-2016-0024?
CVE-2016-0024 is a high vulnerability published on January 13, 2016. The Chakra JavaScript engine in Microsoft Edge allows remote attackers to execute arbitrary code via unspecified vectors, aka "Scripting Engine Memory Corruption Vulnerability."
When was CVE-2016-0024 disclosed?
CVE-2016-0024 was first published in the National Vulnerability Database on January 13, 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-0024 actively exploited?
CVE-2016-0024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-0024?
CVE-2016-0024 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2016-0024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-0024, 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

Explore the affected products and dependency analysis for CVE-2016-0024

Explore →

Is Your Infrastructure Affected by CVE-2016-0024?

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