CVE-2009-5026: The executable comment feature in MySQL 5.0.x before 5.0.93 and 5.1.x before 5.1.50, when running in certain s

Q: How do I fix CVE-2009-5026?

mysql: downgrade or apply the listed mitigation; mysql: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2009-5026 being exploited?

CVE-2009-5026 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2009-5026 affect?

CVE-2009-5026 affects mysql, mysql. Severity is medium (CVSS 6.8). The executable comment feature in MySQL 5.0.x before 5.0.93 and 5.1.x before 5.1.50, when running in certain slave configurations in which the slave is running a newer version than the master, allows remote attackers to execute arbitrary SQ

Q: How urgent is CVE-2009-5026?

Priority 57/100. EPSS top 5%: very likely to be exploited; Public exploit reference; On your watchlist

This month

MEDIUM 6.8WATCHLISTDOWNGRADEDOWNGRADE

CVE-2009-5026 is a medium-severity flaw (CVSS 6.8) affecting mysql, mysql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The executable comment feature in MySQL 5.0.x before 5.0.93 and 5.1.x before 5.1.50, when running in certain slave configurations in which the slave is running a newer version than the master, allows remote attackers to execute arbitrary SQL commands via custom comments.

Why this priority

EPSS top 5%: very likely to be exploited
Public exploit reference
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.8 (Medium)
EPSS exploit chance	7.8% (top 5%)
CISA exploited list	No
Weakness	CWE-89
Published	2012-08-17
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: mysql · oracle

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

Am I affected?

Timeline

2012-08-17 00:55 UTCPublished CVE record published
2026-06-16 23:14 UTCUpdated Record last modified

mysql mysql DOWNGRADE

Affected: 5.0.0 · 5.0.1 · 5.0.2 · 5.0.3 · 5.0.4 · 5.0.5 · 5.0.10 · 5.0.15

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0.0

1. Check installed version

apt-cache policy mysql || rpm -q mysql || mysql --version

2. No fixed release: DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)

apt-cache madison mysql sudo apt install mysql=<VERSION_BEFORE_5.0.0> sudo apt-mark hold mysql

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mysql sudo dnf downgrade mysql-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add mysql

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.

oracle mysql DOWNGRADE

Affected: 5.0.23 · 5.0.41 · 5.0.45 · 5.0.51 · 5.0.67 · 5.0.75 · 5.0.77 · 5.0.81

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0.23

1. Check installed version

apt-cache policy mysql || rpm -q mysql || mysql --version

2. No fixed release: DOWNGRADE to a release before 5.0.23 (Debian / Ubuntu)

apt-cache madison mysql sudo apt install mysql=<VERSION_BEFORE_5.0.23> sudo apt-mark hold mysql

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mysql sudo dnf downgrade mysql-<VERSION_BEFORE_5.0.23> sudo dnf versionlock add mysql

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Oracle MySQL < 5.1.50 - Privilege Escalation

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-2009-5026?

mysql: downgrade or apply the listed mitigation; mysql: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2009-5026 being exploited?

CVE-2009-5026 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-2009-5026 affect?

CVE-2009-5026 affects mysql, mysql. Severity is medium (CVSS 6.8). The executable comment feature in MySQL 5.0.x before 5.0.93 and 5.1.x before 5.1.50, when running in certain slave configurations in which the slave is running a newer version than the master, allows remote attackers to execute arbitrary SQ

How urgent is CVE-2009-5026?

Priority 57/100. EPSS top 5%: very likely to be exploited; Public exploit reference; On your watchlist

Software pages

MySQL vulnerabilities

Related CVEs

CVE-2026-34318 MEDIUM 5.8 UPGRADE Vulnerability in the MySQL Shell product of Oracle MySQL (component: Shell: Core Client)
CVE-2026-34317 MEDIUM 5.0 UPGRADE Vulnerability in the MySQL Shell product of Oracle MySQL (component: Shell: Core Client)
CVE-2026-34319 MEDIUM 5.0 UPGRADE Vulnerability in the MySQL Shell product of Oracle MySQL (component: Shell: Core Client)
CVE-2020-11656 CRITICAL 9.8 UPGRADE MITIGATE In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY
CVE-2025-50104 LOW 2.7 UPGRADE Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL)

References

← Back to latest CVEs