CVE-2026-88816

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — Patch released this week

Also known asEUVD-2026-88343 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to DBI 1.654 or later."

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;

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 30, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

`$dbh->{FetchHashKeyName} = 42; $sth->fetchrow_hashref` segfaults · Advisory · perl5-dbi/dbi · GitHub

https://github.com/perl5-dbi/dbi/security/advisories/GHSA-f4qx-mr9m-q2hq
Web page

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

http://www.openwall.com/lists/oss-security/2026/09/28/13

Vendor and National Authority Advisories for CVE-2026-88816(2)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
oraclepatch2026-11-17oracle
ubuntulibdbi-perl (1.634-1ubuntu0.2+esm5) @ xenial2026-10-28ubuntu

These rows come from Oracle and Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-4, 1.643-4+deb12u1, 1.643-4+deb12u2
  • every version up to 1.643-4+deb12u3: fixed in 1.643-4+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1 ... 1.654-1 (11 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1 ... 1.653-1 (9 versions)
  • every version up to 1.654-1: fixed in 1.654-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 104 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 4 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 06:39 UTCVendor advisory
  2. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-20 11:43 UTCEchelonGraph re-scored
  5. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-11-12 21:32 UTCEchelonGraph re-scored
  13. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-11-05 07:21 UTCEchelonGraph re-scored
  22. 2026-11-05 07:21 UTCVendor advisory
  23. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 75 more
  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-28 17:09 UTCEchelonGraph re-scored
  6. 2026-10-28 17:09 UTCVendor advisory
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-28 15:55 UTCOSV refresh
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-25 13:53 UTCEchelonGraph re-scored
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-20 19:13 UTCEchelonGraph re-scored
  18. 2026-10-20 19:13 UTCVendor advisory
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-18 03:03 UTCEchelonGraph re-scored
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  26. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  27. 2026-10-13 05:01 UTCEchelonGraph re-scored
  28. 2026-10-13 05:01 UTCVendor advisory
  29. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  30. 2026-10-12 14:49 UTCEchelonGraph re-scored
  31. 2026-10-11 19:29 UTCVendor advisory
  32. 2026-10-11 19:15 UTCEchelonGraph re-scored
  33. 2026-10-11 16:32 UTCEchelonGraph re-scored
  34. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  35. 2026-10-11 13:48 UTCEchelonGraph re-scored
  36. 2026-10-11 07:02 UTCEchelonGraph re-scored
  37. 2026-10-11 07:02 UTCVendor advisory
  38. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  39. 2026-10-10 06:07 UTCEchelonGraph re-scored
  40. 2026-10-10 06:07 UTCVendor advisory
  41. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  42. 2026-10-09 17:39 UTCVendor advisory
  43. 2026-10-09 04:31 UTCEchelonGraph re-scored
  44. 2026-10-09 04:31 UTCVendor advisory
  45. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  46. 2026-10-08 16:03 UTCVendor advisory
  47. 2026-10-08 02:57 UTCEchelonGraph re-scored
  48. 2026-10-08 02:57 UTCVendor advisory
  49. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  50. 2026-10-07 14:30 UTCVendor advisory
  51. 2026-10-07 02:00 UTCEchelonGraph re-scored
  52. 2026-10-07 02:00 UTCVendor advisory
  53. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  54. 2026-10-06 13:27 UTCVendor advisory
  55. 2026-10-06 01:00 UTCEchelonGraph re-scored
  56. 2026-10-06 01:00 UTCVendor advisory
  57. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  58. 2026-10-05 12:31 UTCVendor advisory
  59. 2026-10-05 00:05 UTCEchelonGraph re-scored
  60. 2026-10-05 00:05 UTCVendor advisory
  61. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  62. 2026-10-04 11:38 UTCVendor advisory
  63. 2026-10-03 23:11 UTCEchelonGraph re-scored
  64. 2026-10-03 23:11 UTCVendor advisory
  65. 2026-10-03 10:40 UTCVendor advisory
  66. 2026-10-02 22:13 UTCEchelonGraph re-scored
  67. 2026-10-02 22:13 UTCVendor advisory
  68. 2026-10-02 09:46 UTCVendor advisory
  69. 2026-10-01 21:19 UTCEchelonGraph re-scored
  70. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  71. 2026-09-30 19:56 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  72. 2026-09-30 19:55 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  73. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  74. 2026-09-29 19:07 UTCEchelonGraph re-scored
  75. 2026-09-28 19:21 UTCNVD update

Frequently asked(5)

What is CVE-2026-88816?
CVE-2026-88816 is a high-severity vulnerability; its CVE record was published on September 28, 2026. 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)…
When was the CVE record for CVE-2026-88816 published?
The CVE record for CVE-2026-88816 was published on September 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-88816 actively exploited?
CVE-2026-88816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88816?
CVE-2026-88816 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-88816?
A fix for CVE-2026-88816 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to DBI 1.654 or later." The vendor advisories EchelonGraph has for CVE-2026-88816 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-88816 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88816

Explore →

Is Your Infrastructure Affected by CVE-2026-88816?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.