CVE-2006-6948: MyODBC Japanese conversion edition 3.51.06, 2.50.29, and 2.50.25 allows remote attackers to cause a denial of
CVE-2006-6948 is a high-severity flaw (CVSS 7.8) affecting myodbc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
MyODBC Japanese conversion edition 3.51.06, 2.50.29, and 2.50.25 allows remote attackers to cause a denial of service via a certain string in a response, which has unspecified impact on the MySQL database.
Why this priority
- High severity
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.8 (High) |
| EPSS exploit chance | 1.3% (top 29%) |
| CISA exploited list | No |
| Published | 2007-01-23 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2006-6948?
myodbc: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2006-6948 being exploited?
CVE-2006-6948 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2006-6948 affect?
CVE-2006-6948 affects myodbc. Severity is high (CVSS 7.8). MyODBC Japanese conversion edition 3.51.06, 2.50.29, and 2.50.25 allows remote attackers to cause a denial of service via a certain string in a response, which has unspecified impact on the MySQL database.
How urgent is CVE-2006-6948?
Priority 45/100. High severity