CVE-2009-4030

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

MySQL 5.1.x before 5.1.41 allows local users to bypass certain privilege checks by calling CREATE TABLE on a MyISAM table with modified (1) DATA DIRECTORY or (2) INDEX DIRECTORY arguments that are originally associated with pathnames without symlinks, and that can point to tables created at a future time at which a pathname is modified to contain a symlink to a subdirectory of the MySQL data home directory, related to incorrect calculation of the mysql_unpacked_real_data_home value. NOTE: this vulnerability exists because of an incomplete fix for CVE-2008-4098 and CVE-2008-2079.

CVSS v3
—
EG Score
0.0(none)
EPSS
34.5%
KEV
Not listed

Published

November 30, 2009

Last Modified

April 23, 2026

References (42)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumysql-server-5.0 (5.0.67-0ubuntu6.1) @ intrepid2026-05-30ubuntu
ubuntumysql-server-5.1 (5.1.61-0ubuntu0.10.10.1) @ maverick2026-05-30ubuntu
redhatmysql-0:4.1.22-2.el4_8.32010-02-16redhat
redhatmysql-0:5.0.77-4.el5_4.22010-02-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:23 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-05 02:26 UTCEPSS rescore
  6. 2026-07-04 06:27 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-28 14:03 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-28 04:52 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-25 13:46 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:29 UTCEPSS rescore
  18. 2026-06-23 21:29 UTCEPSS rescore
  19. 2026-06-22 14:22 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-21 14:53 UTCEPSS rescore
  22. 2026-06-21 01:56 UTCEPSS rescore
  23. 2026-06-21 01:56 UTCEPSS rescore
  24. 2026-06-19 19:22 UTCEPSS rescore
  25. 2026-06-19 19:22 UTCEPSS rescore
Show 52 more
  1. 2026-06-18 17:49 UTCEPSS rescore
  2. 2026-06-18 17:49 UTCEPSS rescore
  3. 2026-06-17 17:49 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-16 17:49 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-15 17:44 UTCEPSS rescore
  8. 2026-06-13 22:57 UTCEPSS rescore
  9. 2026-06-12 23:08 UTCEPSS rescore
  10. 2026-06-12 23:08 UTCEPSS rescore
  11. 2026-06-10 22:14 UTCEPSS rescore
  12. 2026-06-10 13:17 UTCEPSS rescore
  13. 2026-06-08 14:13 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-06 13:44 UTCEPSS rescore
  17. 2026-06-06 13:44 UTCEPSS rescore
  18. 2026-06-06 13:44 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:07 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-06-01 13:49 UTCEPSS rescore
  28. 2026-05-31 22:28 UTCEPSS rescore
  29. 2026-05-31 22:28 UTCEPSS rescore
  30. 2026-05-31 00:13 UTCEPSS rescore
  31. 2026-05-31 00:13 UTCEPSS rescore
  32. 2026-05-30 14:29 UTCEG score recompute
  33. 2026-05-30 14:29 UTCVendor advisory
  34. 2026-05-30 14:29 UTCGHSA enrichment
  35. 2026-05-29 13:40 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-27 13:38 UTCEPSS rescore
  40. 2026-05-27 13:38 UTCEPSS rescore
  41. 2026-05-26 13:41 UTCEPSS rescore
  42. 2026-05-26 13:41 UTCEPSS rescore
  43. 2026-05-26 07:16 UTCEPSS rescore
  44. 2026-05-26 07:16 UTCEPSS rescore
  45. 2026-05-24 16:43 UTCEPSS rescore
  46. 2026-05-22 21:15 UTCEPSS rescore
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-20 22:37 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 11:21 UTCEPSS rescore
  51. 2026-05-20 11:20 UTCEPSS rescore
  52. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2009-4030?
CVE-2009-4030 is a none vulnerability published on November 30, 2009. MySQL 5.1.x before 5.1.41 allows local users to bypass certain privilege checks by calling CREATE TABLE on a MyISAM table with modified (1) DATA DIRECTORY or (2) INDEX DIRECTORY arguments that are originally associated with pathnames without symlinks, and that can point to tables created at a…
When was CVE-2009-4030 disclosed?
CVE-2009-4030 was first published in the National Vulnerability Database on November 30, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-4030 actively exploited?
CVE-2009-4030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-4030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-4030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-4030

Explore →

Is Your Infrastructure Affected by CVE-2009-4030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs