Quick answers
- Is CVE-2026-88816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88816 being exploited in the wild.
- How severe is CVE-2026-88816?
- Informational severity, published 28 September 2026.
- Which products and versions are affected?
- Perl DBI before 1.654.
- Is there a fix for CVE-2026-88816?
- A patch was published on 2026-09-10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88816 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-88816?
- Check whether you run Perl DBI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the fetchrow_hashref() function in DBI.xs, which uses an invalid pointer when FetchHashKeyName is set to an integer (IV) or floating-point (NV) value. The code calls SvPVX() on the numeric SV without stringifying it first, resulting in a segmentation fault when reading the key name. A fix was applied in version 1.654 by using SvPV_nolen() to force stringification before dereferencing the pointer.
Affected products
- Perl DBI before 1.654
Timeline
- 2026-09-28: disclosed
- 2026-09-10: patched