Threats / ChakraCore / CVE-2018-8298
CVE-2018-8298
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
ChakraCore scripting engine vulnerability
ChakraCore scripting engine contains a type confusion vulnerability enabling remote code execution. Actively exploited in the wild.
Verdict
Today item — known-exploited.
Type confusion in ChakraCore allows attackers to execute arbitrary code remotely. High exploitation prevalence in the wild with EPSS score of 0.89 indicates significant real-world attack activity.
CISA KEV Yes · 2022-03-034EPSS 0.75339 (verify live)5CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
Probability (EPSS)
EPSS 0.75339 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: ChakraCore, ChakraCore scripting engine. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1331 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious script that exploits type confusion in ChakraCore's type system to bypass safety checks.
Business
Attacker gains ability to execute arbitrary code in any application or service running ChakraCore.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit through web content, email attachments, or compromised websites targeting ChakraCore users.
Business
Widespread exposure across browsers, applications, and services using the vulnerable engine.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve remote code execution with the privileges of the affected application or user.
Business
Complete system compromise, data theft, lateral movement, and persistent access to affected infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05