An update for perl-DBI is now available for openEuler-24.03-LTS-SP4 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2026-4254 Final 1.0 1.0 2026-10-16 Initial 2026-10-16 2026-10-16 openEuler SA Tool V1.0 2026-10-16 perl-DBI security update An update for perl-DBI is now available for openEuler-24.03-LTS-SP4 The DBI is the standard database interface module for Perl. It defines a set of methods, variables and conventions that provide a consistent database interface independent of the actual database being used. It is important to remember that the DBI is just an interface. The DBI is a layer of "glue" between an application and one or more database driver modules. It is the driver modules which do most of the real work. The DBI provides a standard interface and framework for the drivers to operate within. Security Fix(es): DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in sql_type_cast_svpv. When casting to SQL_NUMERIC, sql_type_cast_svpv passes the string pointer and length of the SV to grok_number without stringifying it first. An integer (IV) or floating-point (NV) value has no valid string pointer, so grok_number reads from an invalid address, triggering a segmentation fault. This is reachable in Perl using the sql_type_cast function: my $num = 42; DBI::sql_type_cast( $num, DBI::SQL_NUMERIC, 0 );(CVE-2026-88815) 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;(CVE-2026-88816) An update for perl-DBI is now available for openEuler-24.03-LTS-SP4. openEuler Security has rated this update as having a security impact of medium. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Medium perl-DBI https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4254 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-88815 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-88816 https://nvd.nist.gov/vuln/detail/CVE-2026-88815 https://nvd.nist.gov/vuln/detail/CVE-2026-88816 openEuler-24.03-LTS-SP4 perl-DBI-1.648-8.oe2403sp4.aarch64.rpm perl-DBI-debuginfo-1.648-8.oe2403sp4.aarch64.rpm perl-DBI-debugsource-1.648-8.oe2403sp4.aarch64.rpm perl-DBI-1.648-8.oe2403sp4.src.rpm perl-DBI-1.648-8.oe2403sp4.x86_64.rpm perl-DBI-debuginfo-1.648-8.oe2403sp4.x86_64.rpm perl-DBI-debugsource-1.648-8.oe2403sp4.x86_64.rpm perl-DBI-help-1.648-8.oe2403sp4.noarch.rpm DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in sql_type_cast_svpv. When casting to SQL_NUMERIC, sql_type_cast_svpv passes the string pointer and length of the SV to grok_number without stringifying it first. An integer (IV) or floating-point (NV) value has no valid string pointer, so grok_number reads from an invalid address, triggering a segmentation fault. This is reachable in Perl using the sql_type_cast function: my $num = 42; DBI::sql_type_cast( $num, DBI::SQL_NUMERIC, 0 ); 2026-10-16 CVE-2026-88815 openEuler-24.03-LTS-SP4 Medium 6.2 AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H perl-DBI security update 2026-10-16 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4254 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; 2026-10-16 CVE-2026-88816 openEuler-24.03-LTS-SP4 Medium 5.9 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H perl-DBI security update 2026-10-16 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4254