How severe is CVE-2010-3676?

CVE-2010-3676 has a CVSS 2.0 base score of 4.0, rated medium severity.

Is CVE-2010-3676 being actively exploited?

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

What products are affected by CVE-2010-3676?

CVE-2010-3676 primarily affects Mysql. In total, 56 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2010-3676?

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

When was CVE-2010-3676 published?

CVE-2010-3676 was published on 2011-01-11 and last updated on 2026-06-16.

CVE-2010-3676

CVE-2010-3676 is a medium-severity vulnerability in 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: 9% (95th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mysql
Published: 2011-01-11
Last modified: 2026-06-16

Description

storage/innobase/dict/dict0crea.c in mysqld in Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (assertion failure) by modifying the (1) innodb_file_format or (2) innodb_file_per_table configuration parameters for the InnoDB storage engine, then executing a DDL statement.

Frequently asked questions

What is CVE-2010-3676?: storage/innobase/dict/dict0crea.c in mysqld in Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (assertion failure) by modifying the (1) innodb_file_format or (2) innodb_file_per_table configuration parameters for the InnoDB storage engine, then executing a DDL statement.
How severe is CVE-2010-3676?: CVE-2010-3676 has a CVSS 2.0 base score of 4.0, rated medium severity.
Is CVE-2010-3676 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 9% (95th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-3676?: CVE-2010-3676 primarily affects Mysql. In total, 56 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-3676?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2010-3676 published?: CVE-2010-3676 was published on 2011-01-11 and last updated on 2026-06-16.

References

Affected products (56)

cpe:2.3:a:mysql:mysql:5.1.5:*:*:*:*:*:*:*
cpe:2.3:a:mysql:mysql:5.1.23:*:*:*:*:*:*:*
cpe:2.3:a:mysql:mysql:5.1.31:*:*:*:*:*:*:*
cpe:2.3:a:mysql:mysql:5.1.32:*:*:*:*:*:*:*
cpe:2.3:a:mysql:mysql:5.1.34:*:*:*:*:*:*:*
cpe:2.3:a:mysql:mysql:5.1.37:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.2:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.3:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.4:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.6:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.7:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.8:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.9:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.10:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.11:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.12:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.13:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.14:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.15:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.16:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.17:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.18:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.19:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.20:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.21:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.22:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.23:a:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.24:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.25:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.26:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.27:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.28:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.29:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.30:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.31:sp1:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.33:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.34:sp1:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:5.1.35:*:*:*:*:*:*:*

More vulnerabilities in Mysql

CVE-2004-0627 — Critical (CVSS 10.0): The check_scramble_323 function in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to bypass authentication…
CVE-2004-0628 — Critical (CVSS 10.0): Stack-based buffer overflow in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to cause a denial of service…
CVE-2003-0780 — Critical (CVSS 9.0): Buffer overflow in get_salt_from_password from sql_acl.cc for MySQL 4.0.14 and earlier, and 3.23.x, allows attackers…
CVE-2009-2446 — High (CVSS 8.5): Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL…
CVE-2017-15945 — High (CVSS 7.8): The installation scripts in the Gentoo dev-db/mysql, dev-db/mariadb, dev-db/percona-server, dev-db/mysql-cluster, and…
CVE-2013-1492 — High (CVSS 7.5): Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.30, has unspecified impact and…

All CVEs affecting Mysql →