CVE-2018-8229

HIGHNVD 7.58.6▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.6 because EPSS predicts 71% probability of exploitation within the next 30 days (top 0.7% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekWeaponized
8.6EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 71%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 71%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.

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8227.

CVSS v3
7.5
EG Score
8.6(high)
EG Risk
72(Track)
EG Risk 72/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
Severity86% × 45%
Exploitation71% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
71%
EPSS %ILE
99%
KEV
Not listed

Published

June 14, 2018

Last Modified

November 21, 2024

References (8)

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Microsoft.ChakraCore1.2.0 ... 1.8.4 (32 versions)1.8.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× 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:51 UTCEPSS rescore
  2. 2026-07-25 14:14 UTCEPSS rescore
  3. 2026-07-25 14:14 UTCEPSS rescore
  4. 2026-07-24 14:14 UTCEPSS rescore
  5. 2026-07-24 14:14 UTCEPSS rescore
  6. 2026-07-23 01:37 UTCEG score recompute▲ 1.10
  7. 2026-07-22 22:17 UTCEG score recompute
  8. 2026-07-22 14:05 UTCEPSS rescore
  9. 2026-07-21 10:48 UTCOSV refresh
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-20 17:04 UTCEPSS rescore
  12. 2026-07-19 14:28 UTCEPSS rescore
  13. 2026-07-19 14:28 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-15 16:55 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-13 06:10 UTCEPSS rescore
  19. 2026-07-09 19:06 UTCEPSS rescore
  20. 2026-07-08 15:11 UTCEPSS rescore
  21. 2026-07-08 15:11 UTCEPSS rescore
  22. 2026-07-04 06:28 UTCEPSS rescore
  23. 2026-07-04 06:28 UTCEPSS rescore
  24. 2026-07-04 06:26 UTCOSV refresh
  25. 2026-07-01 15:03 UTCEPSS rescore
Show 39 more
  1. 2026-07-01 15:03 UTCEPSS rescore
  2. 2026-06-27 03:06 UTCEPSS rescore
  3. 2026-06-27 03:06 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 18:09 UTCOSV refresh
  14. 2026-06-15 17:45 UTCEPSS rescore
  15. 2026-06-13 22:58 UTCEPSS rescore
  16. 2026-06-12 23:09 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-10 22:16 UTCEPSS rescore
  19. 2026-06-10 13:19 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:45 UTCEPSS rescore
  26. 2026-06-05 22:45 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-02 20:11 UTCEPSS rescore
  30. 2026-06-01 13:50 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 22:29 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-31 00:14 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 06:38 UTCEG score recompute
  38. 2026-05-28 06:38 UTCVendor advisory
  39. 2026-05-26 01:46 UTCOSV refresh

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-45013✓ verified
    First seen Jul 12, 2018

    Microsoft Edge Chakra JIT - Type Confusion with Hoisted SetConcatStrMultiItemBE Instructions

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-8229?
CVE-2018-8229 is a high vulnerability published on June 14, 2018. A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8227.
When was CVE-2018-8229 disclosed?
CVE-2018-8229 was first published in the National Vulnerability Database on June 14, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-8229 actively exploited?
CVE-2018-8229 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71% probability of exploitation in the next 30 days, which ranks it in the top 0.7% of all scored CVEs.
What is the CVSS score of CVE-2018-8229?
CVE-2018-8229 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.6.
How do I remediate CVE-2018-8229?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-8229, 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-2018-8229

Explore →

Is Your Infrastructure Affected by CVE-2018-8229?

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

Start Free Scan →Browse All CVEs