CVE-2026-88816 DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName

High 7.5 Published Updated

An attacker can cause a segmentation fault and denial of service by setting the FetchHashKeyName attribute to a numeric value in the Perl DBI library.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-88816?

CVE-2026-88816 is a high-severity vulnerability, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName.

fetchrow_hashref uses the string pointer of the FetchHashKeyName attribute as the key name without stringifying it first. When FetchHashKeyName has been set to an integer (IV) or floating-point (NV) value, that pointer is invalid, so reading the key name triggers a segmentation fault.

This can be triggered with the following code:

my $dbh = DBI->connect( "dbi:ExampleP:", "", "", { RaiseError => 0, PrintError => 0 } ); $dbh->{FetchHashKeyName} = 42;

my $sth = $dbh->prepare("select mode, size, name from ."); $sth->execute; $sth->fetchrow_hashref;

Weakness: CWE-843

Which versions are affected by CVE-2026-88816?

How do I fix CVE-2026-88816?

Upgrade to a fixed version.

Is CVE-2026-88816 being exploited?

There is no known exploitation of CVE-2026-88816 in the wild and no public exploit code.

Sources

Also known as AZL-105215, BELL-CVE-2026-88816, DEBIAN-CVE-2026-88816, ECHO-5f1f-bfbe-e4bd, GHSA-f4qx-mr9m-q2hq, MINI-jqpv-j697-w57r and 1 more.

Is CVE-2026-88816 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free