CVE-2026-88815 Affecting perl-DBI package, versions <0:1.641-4.el8_10


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.18% (8th 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-ORACLE8-PERLDBI-20883515
  • published13 Oct 2026
  • disclosed28 Sept 2026

Introduced: 28 Sep 2026

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

How to fix?

Upgrade Oracle:8 perl-DBI to version 0:1.641-4.el8_10 or higher.
This issue was patched in ELSA-2026-77576.

NVD Description

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

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 );

CVSS Base Scores

version 3.1