All Threat Alerts
criticalCVE Alert
CVE-2016-6662

Critical Vulnerability: CVE-2016-6662 โ€” oracle, percona โ€” mysql, percona_server

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 af

Thursday, May 14, 2026oracle, perconaVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2016-6662 is rated CRITICAL โ€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: mysql, percona_server, mariadb, debian_linux, openstack, plus 5 other product variants.

Executive Summary

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.

Why It Matters

CVE-2016-6662 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.8/10

Affected Technologies

Vendors: oracle, percona, mariadb, debian, redhat

Products: mysql, percona_server, mariadb, debian_linux, openstack, enterprise_linux, enterprise_linux_desktop, enterprise_linux_server, enterprise_linux_server_aus, enterprise_linux_server_eus, enterprise_linux_server_tus, enterprise_linux_workstation

๐Ÿ›ก๏ธWhat Defenders Should Check

  • Check if you are affected โ€” Review your asset inventory for products listed in CVE-2016-6662.
  • Apply available patches โ€” Visit vendor advisories for the latest security updates.
  • Monitor for exploitation โ€” Check your SIEM/IDS logs for related indicators.
  • Use Vulnios to continuously monitor your exposure to CVE-2016-6662 and similar vulnerabilities.

    References & Sources

    How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for CVE matching against your container images and OS package manifests. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat โ€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Affected Products

    mysqlpercona_servermariadbdebian_linuxopenstackenterprise_linuxenterprise_linux_desktopenterprise_linux_serverenterprise_linux_server_ausenterprise_linux_server_eus

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2016-6662?

    CVE-2016-6662 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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 befor

    Am I affected?

    Check whether your environment runs mysql, percona_server, mariadb, debian_linux, openstack. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2016-6662. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts โ€” all in one platform.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios