Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

45
This month
HIGH 7.8DOWNGRADE

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 score7.8 (High)
EPSS exploit chance1.3% (top 29%)
CISA exploited listNo
Published2007-01-23
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: myodbc

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

myodbc myodbc DOWNGRADE
Affected: japanese_2.50.25 · japanese_2.50.29 · japanese_3.51.06
Fixed in: no fixed release known
Safe to downgrade to: a release before japanese_2.50.25
1. Check installed version
apt-cache policy myodbc || rpm -q myodbc || myodbc --version
2. No fixed release: DOWNGRADE to a release before japanese_2.50.25 (Debian / Ubuntu)
apt-cache madison myodbc sudo apt install myodbc=<VERSION_BEFORE_japanese_2.50.25> sudo apt-mark hold myodbc
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list myodbc sudo dnf downgrade myodbc-<VERSION_BEFORE_japanese_2.50.25> sudo dnf versionlock add myodbc
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
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

Software pages

MySQL vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.