CVE-2016-1251: There is a vulnerability of type use-after-free affecting DBD::mysql (aka DBD-mysql or the Database Interface

This week

HIGH 8.1REMOTEWATCHLISTDOWNGRADE

CVE-2016-1251 is a high-severity flaw (CVSS 8.1) affecting dbd-mysql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

There is a vulnerability of type use-after-free affecting DBD::mysql (aka DBD-mysql or the Database Interface (DBI) MySQL driver for Perl) 3.x and 4.x before 4.041 when used with mysql_server_prepare=1.

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

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

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	3.1% (top 12%)
CISA exploited list	No
Weakness	CWE-416
Published	2016-11-29
Last modified	2026-06-17

Publisher (CNA): Debian GNU/Linux · Vendor: dbd-mysql project

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

Am I affected?

Timeline

2016-11-29 20:59 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

dbd-mysql project dbd-mysql DOWNGRADE

Affected: 3.0000_0 · 3.0001_1 · 3.0001_2 · 3.0001_3 · 3.0002_1 · 3.0002_2 · 3.0002_3 · 3.0002_4

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0000_0

1. Check installed version

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

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

apt-cache madison dbd-mysql sudo apt install dbd-mysql=<VERSION_BEFORE_3.0000_0> sudo apt-mark hold dbd-mysql

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

dnf --showduplicates list dbd-mysql sudo dnf downgrade dbd-mysql-<VERSION_BEFORE_3.0000_0> sudo dnf versionlock add dbd-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.

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-2016-1251?

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

Is CVE-2016-1251 being exploited?

CVE-2016-1251 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-2016-1251 affect?

CVE-2016-1251 affects dbd-mysql. Severity is high (CVSS 8.1). There is a vulnerability of type use-after-free affecting DBD::mysql (aka DBD-mysql or the Database Interface (DBI) MySQL driver for Perl) 3.x and 4.x before 4.041 when used with mysql_server_prepare=1.

How urgent is CVE-2016-1251?

Priority 60/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

MySQL vulnerabilities · Perl vulnerabilities

Related CVEs

CVE-2017-10789 MEDIUM 5.9 UPGRADE The DBD::mysql module through 4.043 for Perl uses the mysql_ssl=1 setting to mean that SSL is optional (even t
CVE-2017-10788 CRITICAL 9.8 UPGRADE The DBD::mysql module through 4.043 for Perl allows remote attackers to cause a denial of service (use-after-f
CVE-2016-1249 MEDIUM 5.9 UPGRADE The DBD::mysql module before 4.039 for Perl, when using server-side prepared statement support, allows attacke
CVE-2016-1246 HIGH 7.5 UPGRADE MITIGATE Buffer overflow in the DBD::mysql module before 4.037 for Perl allows context-dependent attackers to cause a d
CVE-2015-8949 CRITICAL 9.8 DOWNGRADE MITIGATE Use-after-free vulnerability in the my_login function in DBD::mysql before 4.033_01 allows attackers to have u

References

← Back to latest CVEs