CVE-2009-2446

CVE-2009-2446 is a high-severity vulnerability in Mysql with a CVSS 2.0 base score of 8.5. Its EPSS exploit-prediction score of 11% places it in the 95th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-134.

Key facts

Description

Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL 4.0.0 through 5.0.83 allow remote authenticated users to cause a denial of service (daemon crash) and possibly have unspecified other impact via format string specifiers in a database name in a (1) COM_CREATE_DB or (2) COM_DROP_DB request. NOTE: some of these details are obtained from third party information.

Frequently asked questions

What is CVE-2009-2446?
Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL 4.0.0 through 5.0.83 allow remote authenticated users to cause a denial of service (daemon crash) and possibly have unspecified other impact via format string specifiers in a database name in a (1) COM_CREATE_DB or (2) COM_DROP_DB request. NOTE: some of these details are obtained from third party information.
How severe is CVE-2009-2446?
CVE-2009-2446 has a CVSS 2.0 base score of 8.5, rated high severity.
Is CVE-2009-2446 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 11% (95th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2446?
CVE-2009-2446 primarily affects Mysql. In total, 115 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-2446?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-2446 published?
CVE-2009-2446 was published on 2009-07-13 and last updated on 2026-06-16.

References

Affected products (115)

More vulnerabilities in Mysql

All CVEs affecting Mysql →

Other CWE-134 vulnerabilities

Browse all CWE-134 vulnerabilities →