CVE-2026-88816 Affecting libdbi-perl package, versions <1.643-4+deb12u3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.62% (48th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-LIBDBIPERL-20137990
  • published25 Sept 2026
  • disclosed28 Sept 2026

Introduced: 25 Sep 2026

NewCVE-2026-88816  (opens in a new tab)

How to fix?

Upgrade Echo:latest libdbi-perl to version 1.643-4+deb12u3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libdbi-perl package and not the libdbi-perl package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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;

CVSS Base Scores

version 3.1