CVE-2026-88815: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
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 );
AI Analysis
Technical Summary
In DBI versions prior to 1.654 for Perl, the function sql_type_cast_svpv incorrectly handles numeric values when casting to SQL_NUMERIC. Instead of converting the numeric scalar value to a string, it passes the string pointer and length directly to grok_number. Since integer (IV) or floating-point (NV) values lack valid string pointers, grok_number attempts to read from an invalid memory address, causing a segmentation fault. This vulnerability is reachable via the sql_type_cast function in Perl code.
Potential Impact
The vulnerability causes a segmentation fault when processing numeric values in SQL type casting, potentially leading to denial of service in applications using the affected DBI versions. There is no indication of code execution or data corruption beyond the crash.
Mitigation Recommendations
No official patch or remediation information is provided. Users should upgrade to DBI version 1.654 or later once available to resolve this issue. Until then, avoid passing numeric values directly to sql_type_cast with SQL_NUMERIC or apply workarounds to ensure values are stringified before casting. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-88815: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
Description
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 );
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In DBI versions prior to 1.654 for Perl, the function sql_type_cast_svpv incorrectly handles numeric values when casting to SQL_NUMERIC. Instead of converting the numeric scalar value to a string, it passes the string pointer and length directly to grok_number. Since integer (IV) or floating-point (NV) values lack valid string pointers, grok_number attempts to read from an invalid memory address, causing a segmentation fault. This vulnerability is reachable via the sql_type_cast function in Perl code.
Potential Impact
The vulnerability causes a segmentation fault when processing numeric values in SQL type casting, potentially leading to denial of service in applications using the affected DBI versions. There is no indication of code execution or data corruption beyond the crash.
Mitigation Recommendations
No official patch or remediation information is provided. Users should upgrade to DBI version 1.654 or later once available to resolve this issue. Until then, avoid passing numeric values directly to sql_type_cast with SQL_NUMERIC or apply workarounds to ensure values are stringified before casting. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-09-10T08:47:49.901Z
- State
- PUBLISHED
Threat ID: 6aba96ccf7a7c54106ee8aed
Added to database: 09/28/2026, 16:33:16 UTC
Last enriched: 09/28/2026, 16:47:53 UTC
Last updated: 09/29/2026, 01:57:22 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.