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

> An attacker can cause a segmentation fault and denial of service by setting the FetchHashKeyName attribute to a numeric value in the Perl DBI library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** AZL-105215, BELL-CVE-2026-88816, DEBIAN-CVE-2026-88816, ECHO-5f1f-bfbe-e4bd, GHSA-f4qx-mr9m-q2hq, MINI-jqpv-j697-w57r, UBUNTU-CVE-2026-88816

## What is CVE-2026-88816?

CVE-2026-88816 is a high-severity vulnerability, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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;

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-88816 being exploited?

There is no known exploitation of CVE-2026-88816 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88816 is a high-severity vulnerability, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88816 in the wild and no public exploit code.

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-88816/ (Markdown: https://insights.sbomify.com/CVE-2026-88816/index.md)
```

## Sources

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

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