Skip to main content
VulnerabilityPublished Updated

CVE-2026-88816: DBI (Perl module) · Type Confusion

Affects DBI (Perl module)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.654 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.654
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade DBI (Perl module) to 1.654.

Affected software

ProductAffectedFixed in
CPANDBIpkg:cpan/DBIOther threatsAffected
  • <1.654
Fixed in
  • 1.654

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in DBI version 1.654 and later. Users should upgrade to version 1.654 or newer to remediate this issue. No other mitigation or workaround is indicated in the available data.

Description

CVE-2026-88816 is a high-severity vulnerability in Perl's DBI module versions before 1.654. It involves a type confusion issue where numeric values are incorrectly treated as strings in the FetchHashKeyName attribute. This leads to a segmentation fault when fetchrow_hashref attempts to use an invalid pointer as a hash key name. The flaw can be triggered by setting FetchHashKeyName to a numeric value such as an integer or floating-point number.

References

Community reviews

Loading reviews…