CVE-2026-88815

What it is

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

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-28 17:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-30 20:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 6.2 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-28 17:17 UTC

Last modified

2026-09-30 20:17 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-843

Record status

Deferred

Attack profile CVSS 3.1 · 6.2

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-88815.md and follow it. Check whether this project is affected by CVE-2026-88815. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge