basicsecurity.net
Proof, not just disclosure.
Threats / ChakraCore / CVE-2018-8298
CVE-2018-8298 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-033EPSS 0.75339 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
CISA KEV ↗Confirmed
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
Affected: ChakraCore, ChakraCore scripting engine. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-843 · Type ConfusionMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.