DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName
CVE-2026-88816 is fixed in 2 products on 1 platform, first by libdbi-perl 1.647-1ubuntu0.26.04.4, released September 28, 2026. It is not reported as exploited. Patch Radar priority: High.
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;
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libdbi-perl · Debian 12.15 (bookworm) | 1.643-4+deb12u3 | DEBIAN-CVE-2026-88816 | Sep 29, 2026 |
| libdbi-perl · Debian 14 | 1.654-1 | DEBIAN-CVE-2026-88816 | Sep 29, 2026 |
| libdbi-perl · Ubuntu 18.04.6 LTS (bionic) | 1.640-1ubuntu0.3+esm4 | libdbi-perl 1.640-1ubuntu0.3+esm4 | Oct 12, 2026 |
| libdbi-perl · Ubuntu 20.04 LTS (focal) | 1.643-1ubuntu0.1+esm4 | libdbi-perl 1.643-1ubuntu0.1+esm4 | Oct 12, 2026 |
| libdbi-perl · Ubuntu 22.04.1 LTS (jammy) | 1.643-3ubuntu0.4 | libdbi-perl 1.643-3ubuntu0.4 | Oct 12, 2026 |
| libdbi-perl · Ubuntu 24.04.5 LTS (noble) | 1.643-4ubuntu0.4 | libdbi-perl 1.643-4ubuntu0.4 | Oct 12, 2026 |
| libdbi-perl · Ubuntu 26.04.1 LTS (resolute) | 1.647-1ubuntu0.26.04.4 | libdbi-perl 1.647-1ubuntu0.26.04.4 | Sep 28, 2026 |
| perl-DBI · sles 15.7 | 1.647.0-150600.12.26.1 | SUSE-SU-2026:4805-1 | Nov 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.