Vulnerabilities

Vulnerability · CVE-2006-4226

MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database…

Published Aug 18, 2006 · catalog updated Jun 16, 2026 · Oracle

Check if you run it

No confirmed exploitation is on record for CVE-2006-4226. EPSS is 3.07%. Act only if a listed version of Oracle is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low3.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
3.07%
Remediation
Advisory link
Affected products
cpe mysql/mysql

MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe mysql/mysql4.1.0
  • cpe mysql/mysql4.1.10
  • cpe mysql/mysql4.1.12
  • cpe mysql/mysql4.1.13
  • cpe mysql/mysql4.1.14
  • cpe mysql/mysql4.1.15
  • cpe mysql/mysql4.1.2
  • cpe mysql/mysql4.1.3
  • cpe mysql/mysql4.1.8
  • cpe mysql/mysql5.0.0
  • cpe mysql/mysql5.0.1
  • cpe mysql/mysql5.0.2

How to fix CVE-2006-4226

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2006-4226. EPSS is 3.07%. Act only if a listed version of Oracle is installed.

Which versions are affected?

Compare what you have installed with 4.1.0, 4.1.10, 4.1.12, 4.1.13, 4.1.14, 4.1.15. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 3.07%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 18, 2006 · Oracle Critical Patch Updates

    Detected

    MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.

  2. Jun 16, 2026 · Oracle Critical Patch Updates

    Updated

    MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.

Sources

  • CVE.orgVulnerability recordCVE-2006-4226

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2006-4226

    30-day exploitation probability 3.1%

    first.org
  • Oracle Critical Patch UpdatesVendor advisoryCVE-2006-4226

    MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.