CVE-2018-3187

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 3%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer). Supported versions that are affected are 5.7.23 and prior and 8.0.12 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.0 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
84.8%
KEV
Not listed

Published

October 17, 2018

Last Modified

November 21, 2024

References (12)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumysql-testsuite-5.7 (5.7.24-0ubuntu0.18.04.1) @ bionic2026-05-28ubuntu
redhatrh-mysql57-mysql-0:5.7.24-1.el72018-11-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(2)

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2018-3187?
CVE-2018-3187 is a medium vulnerability published on October 17, 2018. Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer). Supported versions that are affected are 5.7.23 and prior and 8.0.12 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise…
When was CVE-2018-3187 disclosed?
CVE-2018-3187 was first published in the National Vulnerability Database on October 17, 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-3187 actively exploited?
CVE-2018-3187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-3187?
CVE-2018-3187 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2018-3187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-3187, 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-3187

Explore →

Is Your Infrastructure Affected by CVE-2018-3187?

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

Start Free Scan →Browse All CVEs