CVE-2018-0840

HIGHNVD 7.58.1▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 54%
CISA-KEV: Not listedEPSS: 54%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Internet Explorer in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, and Internet Explorer and Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0834, CVE-2018-0835, CVE-2018-0836, CVE-2018-0837, CVE-2018-0838, CVE-2018-0856, CVE-2018-0857, CVE-2018-0858, CVE-2018-0859, CVE-2018-0860, CVE-2018-0861, and CVE-2018-0866.

CVSS v3
7.5
EG Score
8.1(high)
EG Risk
67(Track)
EG Risk 67/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
Severity81% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.9%
KEV
Not listed

Published

February 15, 2018

Last Modified

November 21, 2024

References (10)

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

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-44077✓ verified
    First seen Feb 15, 2018

    Microsoft Edge Chakra JIT - ImplicitCallFlags Checks Bypass

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-0840?
CVE-2018-0840 is a high vulnerability published on February 15, 2018. Internet Explorer in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, and Internet Explorer and Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the scripting…
When was CVE-2018-0840 disclosed?
CVE-2018-0840 was first published in the National Vulnerability Database on February 15, 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-0840 actively exploited?
CVE-2018-0840 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-0840?
CVE-2018-0840 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.1.
How do I remediate CVE-2018-0840?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-0840, 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-2018-0840

Explore →

Is Your Infrastructure Affected by CVE-2018-0840?

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

Start Free Scan →Browse All CVEs