# CVE-2026-88815: DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in sql_type_cast_svpv

> An attacker can cause a segmentation fault and denial of service by passing numeric values to the sql_type_cast function in the Perl DBI library.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** ALSA-2026:76760, ALSA-2026:76762, ALSA-2026:77576, ALSA-2026:85916, AZL-105212, BELL-CVE-2026-88815, CLSA-2026-1791807966, CLSA-2026-1791814009, DEBIAN-CVE-2026-88815, ECHO-fc84-f286-7f43, GHSA-c8vq-w3wr-6979, MINI-r3h7-42r7-vpgh, RHSA-2026:76760, RHSA-2026:76762, RHSA-2026:77576, RLSA-2026:76760, RLSA-2026:76762, RLSA-2026:77576, RLSA-2026:85916, UBUNTU-CVE-2026-88815

## What is CVE-2026-88815?

CVE-2026-88815 is a medium-severity vulnerability in perl-DBI, published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-88815?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-DBI` | AlmaLinux:10 | All versions | 1.643-26.el10_2.7 |
| `perl-DBI` | AlmaLinux:8 | All versions | 1.641-11.module_el8.10.0+4309+f7cd2555 |
| `perl-DBI` | AlmaLinux:8 | All versions | 1.641-4.el8_10 |
| `perl-DBI` | AlmaLinux:9 | All versions | 1.643-9.el9_8.7 |
| `perl-DBI` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.643-26.el10_2.7 |
| `perl-DBI-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.643-26.el10_2.7 |
| `perl-DBI-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.643-26.el10_2.7 |
| `perl-DBI` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.641-4.el8_10 |
| `perl-DBI-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.641-4.el8_10 |
| `perl-DBI-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.641-4.el8_10 |
| `perl-DBI` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.643-9.el9_8.7 |
| `perl-DBI-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.643-9.el9_8.7 |
| `perl-DBI-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.643-9.el9_8.7 |
| `perl-DBI` | Rocky Linux:10 | All versions | 0:1.643-26.el10_2.7 |
| `perl-DBI` | Rocky Linux:8 | All versions | 0:1.641-11.module+el8.10.0+40389+22ad89a7 |
| `perl-DBI` | Rocky Linux:8 | All versions | 0:1.641-11.module+el8.10.0+40389+69d937a8 |
| `perl-DBI` | Rocky Linux:8 | All versions | 0:1.641-11.module+el8.10.0+40389+75d7e2a7 |
| `perl-DBI` | Rocky Linux:8 | All versions | 0:1.641-11.module+el8.10.0+40389+be9de675 |
| `perl-DBI` | Rocky Linux:8 | All versions | 0:1.641-4.el8_10 |
| `perl-DBI` | Rocky Linux:9 | All versions | 0:1.643-9.el9_8.7 |

## How do I fix CVE-2026-88815?

Upgrade to a fixed version.

## Is CVE-2026-88815 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88815 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88815 and fix it if it is affected.

What it is: CVE-2026-88815 is a medium-severity vulnerability in perl-DBI, published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88815 exists.

Affected product: perl-DBI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88815/ (Markdown: https://insights.sbomify.com/CVE-2026-88815/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88815
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88815
- OSV: https://osv.dev/vulnerability/CVE-2026-88815

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88815/
Summaries are generated and may contain mistakes; the official description above is the record.