How severe is CVE-2016-0654?

CVE-2016-0654 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2016-0654 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-0654?

CVE-2016-0654 affects Oracle Mysql. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2016-0654?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2016-0654 published?

CVE-2016-0654 was published on 2016-04-21 and last updated on 2026-06-17.

CVE-2016-0654

CVE-2016-0654 is a medium-severity vulnerability in Oracle Mysql with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v2: 3.5
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Mysql
Published: 2016-04-21
Last modified: 2026-06-17

Description

Unspecified vulnerability in Oracle MySQL 5.7.10 and earlier allows local users to affect availability via vectors related to InnoDB, a different vulnerability than CVE-2016-0656.

Frequently asked questions

What is CVE-2016-0654?: Unspecified vulnerability in Oracle MySQL 5.7.10 and earlier allows local users to affect availability via vectors related to InnoDB, a different vulnerability than CVE-2016-0656.
How severe is CVE-2016-0654?: CVE-2016-0654 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2016-0654 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-0654?: CVE-2016-0654 affects Oracle Mysql. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-0654?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-0654 published?: CVE-2016-0654 was published on 2016-04-21 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:oracle:mysql:*:*:*:*:*:*:*:*

More vulnerabilities in Oracle Mysql

CVE-2012-2750 — Critical (CVSS 10.0): Unspecified vulnerability in MySQL 5.5.x before 5.5.23 has unknown impact and attack vectors related to a "Security…
CVE-2004-0836 — Critical (CVSS 10.0): Buffer overflow in the mysql_real_connect function in MySQL 4.x before 4.0.21, and 3.x before 3.23.49, allows remote…
CVE-2020-11656 — Critical (CVSS 9.8): In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause…
CVE-2019-14540 — Critical (CVSS 9.8): A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to…
CVE-2016-9843 — Critical (CVSS 9.8): The crc32_big function in crc32.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact via…
CVE-2016-9841 — Critical (CVSS 9.8): inffast.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper…

All CVEs affecting Oracle Mysql →

Threat intelligence

Threat-intel indicators referencing this CVE:

85.95.166.40 (ipv4-addr)
132.148.155.138 (ipv4-addr)
180.76.184.79 (ipv4-addr)
159.253.22.85 (ipv4-addr)
122.51.73.24 (ipv4-addr)
193.151.90.204 (ipv4-addr)