CVE-2016-6662

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 68%
CISA-KEV: Not listedEPSS: 68%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.27, and 10.1.x before 10.1.17; and Percona Server before 5.5.51-38.1, 5.6.x before 5.6.32-78.0, and 5.7.x before 5.7.14-7 allow local users to create arbitrary configurations and bypass certain protection mechanisms by setting general_log_file to a my.cnf configuration. NOTE: this can be leveraged to execute arbitrary code with root privileges by setting malloc_lib. NOTE: the affected MySQL version information is from Oracle's October 2016 CPU. Oracle has not commented on third-party claims that the issue was silently patched in MySQL 5.5.52, 5.6.33, and 5.7.15.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
76(Track*)
EG Risk 76/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
Severity98% × 45%
Exploitation68% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.2%
KEV
Not listed

Published

September 20, 2016

Last Modified

May 6, 2026

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumysql-testsuite-5.7 (5.7.15-0ubuntu0.16.04.1) @ xenial2026-05-20ubuntu
redhatmysql-0:5.1.73-8.el6_82017-01-24redhat
redhatrh-mariadb101-mariadb-1:10.1.19-6.el72016-12-08redhat
redhatrh-mariadb100-mariadb-1:10.0.28-5.el72016-12-08redhat
redhatrh-mysql56-mysql-0:5.6.34-2.el72016-11-15redhat
redhatmariadb-1:5.5.52-1.el72016-11-03redhat
redhatmariadb55-mariadb-0:5.5.53-1.el72016-10-31redhat
redhatmysql55-mysql-0:5.5.52-1.el72016-10-31redhat
redhatmariadb-galera-1:5.5.42-5.el7ost2016-10-18redhat
redhatmariadb-galera-1:5.5.42-1.2.el7ost2016-10-13redhat
redhatmariadb-galera-0:5.5.42-1.1.el6ost2016-10-13redhat

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

(14)

Data Freshness Timeline

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCMAYASEVEN/CVE-2016-6662
    First seen May 1, 2017

    From SQL injection to root shell with CVE-2016-6662 by MaYaSeVeN

    Open source ↗
  • GitHub PoCAshrafdev/MySQL-Remote-Root-Code-Execution
    First seen Sep 20, 2016

    0ldSQL_MySQL_RCE_exploit.py (ver. 1.0) (CVE-2016-6662) MySQL Remote Root Code Execution / Privesc PoC Exploit For testing purposes only. Do no harm.

    Open source ↗
  • Exploit-DBEDB-40360
    First seen Sep 12, 2016

    MySQL / MariaDB / PerconaDB 5.5.51/5.6.32/5.7.14 - Code Execution / Privilege Escalation

    Open source ↗

Frequently asked(5)

What is CVE-2016-6662?
CVE-2016-6662 is a critical vulnerability published on September 20, 2016. Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.27, and 10.1.x before 10.1.17; and Percona Server before 5.5.51-38.1, 5.6.x before 5.6.32-78.0, and 5.7.x before 5.7.14-7 allow local users to create arbitrary configurations and…
When was CVE-2016-6662 disclosed?
CVE-2016-6662 was first published in the National Vulnerability Database on September 20, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-6662 actively exploited?
CVE-2016-6662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-6662?
CVE-2016-6662 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-6662?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-6662, 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-2016-6662

Explore →

Is Your Infrastructure Affected by CVE-2016-6662?

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