How severe is CVE-2015-4800?

CVE-2015-4800 has a CVSS 2.0 base score of 4.0, rated medium severity.

Is CVE-2015-4800 being actively exploited?

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

What products are affected by CVE-2015-4800?

CVE-2015-4800 primarily affects Oracle Mysql. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2015-4800?

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

When was CVE-2015-4800 published?

CVE-2015-4800 was published on 2015-10-21 and last updated on 2026-06-17.

CVE-2015-4800

CVE-2015-4800 is a medium-severity vulnerability in Oracle Mysql with a CVSS 2.0 base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.0)
EPSS exploit prediction: 2% (81st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Mysql
Published: 2015-10-21
Last modified: 2026-06-17

Description

Unspecified vulnerability in Oracle MySQL Server 5.6.26 and earlier allows remote authenticated users to affect availability via unknown vectors related to Server : Optimizer.

Frequently asked questions

What is CVE-2015-4800?: Unspecified vulnerability in Oracle MySQL Server 5.6.26 and earlier allows remote authenticated users to affect availability via unknown vectors related to Server : Optimizer.
How severe is CVE-2015-4800?: CVE-2015-4800 has a CVSS 2.0 base score of 4.0, rated medium severity.
Is CVE-2015-4800 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-4800?: CVE-2015-4800 primarily affects Oracle Mysql. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-4800?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2015-4800 published?: CVE-2015-4800 was published on 2015-10-21 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*
cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*
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 →