A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore. This CVE ID is unique from CVE-2018-8242, CVE-2018-8283, CVE-2018-8287, CVE-2018-8288, CVE-2018-8291, CVE-2018-8296.
CVE-2018-8298
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 9.0(high)
- EPSS
- 99.5%
- KEV
- ⚠ Exploited
Published
July 11, 2018
Last Modified
October 28, 2025
Advisory Details (4)
Auto-updated Jun 6, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-8298Microsoft Edge Chakra JIT - InitializeNumberFormat and InitializeDateTimeFormat Type Confusion - Windows dos Exploit
https://www.exploit-db.com/exploits/45217/Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8298Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| Microsoft.ChakraCore | 1.10.0 ... 1.8.5 (34 versions) | 1.10.1 | — |
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 90× in last 7d / 377× 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.
Showing the most recent 100 of 537 total refreshes for this CVE.
- 2026-07-12 02:07 UTCEG score recompute
- 2026-07-12 02:07 UTCVendor advisory
- 2026-07-11 22:05 UTCEG score recompute
- 2026-07-11 22:05 UTCVendor advisory
- 2026-07-11 18:03 UTCEG score recompute
- 2026-07-11 18:03 UTCVendor advisory
- 2026-07-11 14:02 UTCEG score recompute
- 2026-07-11 14:02 UTCVendor advisory
- 2026-07-11 09:58 UTCEG score recompute
- 2026-07-11 09:58 UTCVendor advisory
- 2026-07-11 05:56 UTCEG score recompute
- 2026-07-11 05:56 UTCVendor advisory
- 2026-07-11 01:54 UTCEG score recompute
- 2026-07-11 01:54 UTCVendor advisory
- 2026-07-10 21:51 UTCEG score recompute
- 2026-07-10 21:51 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 17:49 UTCEG score recompute
- 2026-07-10 17:49 UTCVendor advisory
- 2026-07-10 13:48 UTCEG score recompute
- 2026-07-10 13:48 UTCVendor advisory
- 2026-07-10 09:45 UTCEG score recompute
- 2026-07-10 09:45 UTCVendor advisory
- 2026-07-10 05:39 UTCEG score recompute
- 2026-07-10 05:39 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-10 01:36 UTCEG score recompute
- 2026-07-10 01:36 UTCVendor advisory
- 2026-07-09 21:34 UTCEG score recompute
- 2026-07-09 21:34 UTCVendor advisory
- 2026-07-09 17:30 UTCEG score recompute
- 2026-07-09 17:30 UTCVendor advisory
- 2026-07-09 13:29 UTCEG score recompute
- 2026-07-09 13:29 UTCVendor advisory
- 2026-07-09 09:27 UTCEG score recompute
- 2026-07-09 09:27 UTCVendor advisory
- 2026-07-09 05:25 UTCEG score recompute
- 2026-07-09 05:25 UTCVendor advisory
- 2026-07-09 01:24 UTCEG score recompute
- 2026-07-09 01:24 UTCVendor advisory
- 2026-07-08 21:21 UTCEG score recompute
- 2026-07-08 21:21 UTCVendor advisory
- 2026-07-08 17:20 UTCEG score recompute
- 2026-07-08 17:20 UTCVendor advisory
- 2026-07-08 15:11 UTCEPSS rescore
- 2026-07-08 15:11 UTCEPSS rescore
- 2026-07-08 13:17 UTCEG score recompute
- 2026-07-08 13:17 UTCVendor advisory
- 2026-07-08 09:14 UTCEG score recompute
- 2026-07-08 09:14 UTCVendor advisory
- 2026-07-08 05:12 UTCEG score recompute
- 2026-07-08 05:12 UTCVendor advisory
- 2026-07-08 01:11 UTCEG score recompute
- 2026-07-08 01:11 UTCVendor advisory
- 2026-07-07 21:09 UTCEG score recompute
- 2026-07-07 19:01 UTCCISA KEV update
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 17:07 UTCEG score recompute
- 2026-07-07 17:07 UTCVendor advisory
- 2026-07-07 13:04 UTCEG score recompute
- 2026-07-07 13:04 UTCVendor advisory
- 2026-07-07 09:02 UTCEG score recompute
- 2026-07-07 09:02 UTCVendor advisory
- 2026-07-07 04:59 UTCEG score recompute
- 2026-07-07 04:59 UTCVendor advisory
- 2026-07-07 00:55 UTCEG score recompute
- 2026-07-07 00:55 UTCVendor advisory
- 2026-07-06 20:53 UTCEG score recompute
- 2026-07-06 20:53 UTCVendor advisory
- 2026-07-06 16:51 UTCEG score recompute
- 2026-07-06 16:51 UTCVendor advisory
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 12:47 UTCEG score recompute
- 2026-07-06 12:47 UTCVendor advisory
- 2026-07-06 08:46 UTCEG score recompute
- 2026-07-06 08:46 UTCVendor advisory
- 2026-07-06 04:43 UTCEG score recompute
- 2026-07-06 04:43 UTCVendor advisory
- 2026-07-06 00:39 UTCEG score recompute
- 2026-07-06 00:39 UTCVendor advisory
- 2026-07-05 20:37 UTCEG score recompute
- 2026-07-05 20:37 UTCVendor advisory
- 2026-07-05 16:36 UTCEG score recompute
- 2026-07-05 16:36 UTCVendor advisory
- 2026-07-05 12:34 UTCEG score recompute
- 2026-07-05 12:34 UTCVendor advisory
- 2026-07-05 08:33 UTCEG score recompute
- 2026-07-05 08:33 UTCVendor advisory
- 2026-07-05 04:32 UTCEG score recompute
- 2026-07-05 04:32 UTCVendor advisory
- 2026-07-05 00:28 UTCEG score recompute
- 2026-07-05 00:28 UTCVendor advisory
- 2026-07-04 20:26 UTCEG score recompute
- 2026-07-04 20:26 UTCVendor advisory
- 2026-07-04 16:25 UTCEG score recompute
- 2026-07-04 16:25 UTCVendor advisory
- 2026-07-04 12:21 UTCEG score recompute
- 2026-07-04 12:21 UTCVendor advisory
- 2026-07-04 08:20 UTCEG score recompute
- 2026-07-04 08:20 UTCVendor advisory
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-45217✓ verifiedFirst seen Aug 17, 2018
Microsoft Edge Chakra JIT - InitializeNumberFormat and InitializeDateTimeFormat Type Confusion
Open source ↗
Frequently asked(6)
What is CVE-2018-8298?
When was CVE-2018-8298 disclosed?
Is CVE-2018-8298 actively exploited?
What is the CVSS score of CVE-2018-8298?
Which products are affected by CVE-2018-8298?
How do I remediate CVE-2018-8298?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-8298
Is Your Infrastructure Affected by CVE-2018-8298?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.