CVE-2026-14739

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2026-42124 (ENISA EUVD) · GHSA-w9gf-c5hh-cc8w (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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: 9.8Exploit: 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 version 1.650 or later."

DBI versions before 1.650 for Perl have a heap overflow when preparsing SQL statements with an extreme number of placeholders.

The fix for CVE-2026-10879 did not allocate enough memory to handle approximately 1.2-million placeholders.

DBI version 1.650 sets a hard limit of 99,999 placeholders.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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 total (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
35th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 3 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 total (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)3 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 total (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

July 7, 2026

Last Modified

October 25, 2026

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatperl-DBI-0:1.641-2.el8_102026-09-02redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatperl-DBI:1.641-8100020260805130201.69ef70f82026-08-10redhat
redhatperl-DBI-0:1.643-26.el10_2.32026-08-03redhat
redhatperl-DBI-0:1.643-9.el9_8.32026-08-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
perl-dbi—
  • every version up to 1.651-r0: fixed in 1.651-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-3 ... 1.651-1 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-4, 1.643-4+deb12u1
  • every version up to 1.643-4+deb12u2: fixed in 1.643-4+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1 ... 1.652-1 (7 versions)
  • every version up to 1.652-2~deb13u1: fixed in 1.652-2~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1, 1.648-1, 1.649-1
  • every version up to 1.650-1: fixed in 1.650-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 28× in last 7d / 98× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 672 refreshes 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 572 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 09:21 UTCEG score recompute
  2. 2026-11-02 09:21 UTCVendor advisory
  3. 2026-11-02 09:21 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-11-01 08:06 UTCEG score recompute
  6. 2026-11-01 08:06 UTCVendor advisory
  7. 2026-11-01 08:06 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-31 06:50 UTCEG score recompute
  10. 2026-10-31 06:50 UTCVendor advisory
  11. 2026-10-31 06:50 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-30 05:36 UTCEG score recompute
  14. 2026-10-30 05:36 UTCVendor advisory
  15. 2026-10-30 05:35 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-29 04:21 UTCEG score recompute
  18. 2026-10-29 04:21 UTCVendor advisory
  19. 2026-10-29 04:21 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-10-28 03:01 UTCEG score recompute
  22. 2026-10-28 03:01 UTCVendor advisory
  23. 2026-10-28 03:00 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-10-27 01:37 UTCEG score recompute
Show 75 more
  1. 2026-10-27 01:37 UTCVendor advisory
  2. 2026-10-27 01:37 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-25 20:26 UTCEG score recompute
  5. 2026-10-25 20:26 UTCVendor advisory
  6. 2026-10-25 20:26 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-25 14:48 UTCEG score recompute
  9. 2026-10-25 08:07 UTCEG score recompute
  10. 2026-10-25 08:07 UTCVendor advisory
  11. 2026-10-25 08:07 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-24 06:52 UTCEG score recompute
  14. 2026-10-24 06:52 UTCVendor advisory
  15. 2026-10-24 06:51 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-23 05:37 UTCEG score recompute
  18. 2026-10-23 05:37 UTCVendor advisory
  19. 2026-10-23 05:37 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-22 04:22 UTCEG score recompute
  22. 2026-10-22 04:22 UTCVendor advisory
  23. 2026-10-22 04:22 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-10-21 03:07 UTCEG score recompute
  26. 2026-10-21 03:07 UTCVendor advisory
  27. 2026-10-21 03:06 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-10-20 01:52 UTCEG score recompute
  30. 2026-10-20 01:52 UTCVendor advisory
  31. 2026-10-20 01:51 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-10-19 00:35 UTCEG score recompute
  34. 2026-10-19 00:35 UTCVendor advisory
  35. 2026-10-19 00:34 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-10-18 05:02 UTCEG score recompute
  38. 2026-10-17 23:18 UTCEG score recompute
  39. 2026-10-17 23:18 UTCVendor advisory
  40. 2026-10-17 23:18 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  42. 2026-10-16 22:02 UTCEG score recompute
  43. 2026-10-16 22:02 UTCVendor advisory
  44. 2026-10-16 22:02 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-10-15 18:32 UTCEG score recompute
  47. 2026-10-15 18:32 UTCVendor advisory
  48. 2026-10-15 18:32 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  50. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-10-14 12:11 UTCEG score recompute
  52. 2026-10-14 12:11 UTCVendor advisory
  53. 2026-10-14 12:11 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-10-13 10:57 UTCEG score recompute
  56. 2026-10-13 10:57 UTCVendor advisory
  57. 2026-10-13 10:57 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-10-12 16:33 UTCEG score recompute
  60. 2026-10-12 09:41 UTCVendor advisory
  61. 2026-10-12 09:41 UTCGHSA enrichmentGHSA-w9gf-c5hh-cc8w · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-11 20:10 UTCEG score recompute
  63. 2026-10-11 18:22 UTCEG score recompute
  64. 2026-10-11 14:56 UTCEG score recompute
  65. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  66. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  67. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  68. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  69. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  70. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  71. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  72. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  73. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  74. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  75. 2026-10-01 16:25 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-14739?
CVE-2026-14739 is a critical-severity vulnerability; its CVE record was published on July 7, 2026. DBI versions before 1.650 for Perl have a heap overflow when preparsing SQL statements with an extreme number of placeholders. The fix for CVE-2026-10879 did not allocate enough memory to handle approximately 1.2-million placeholders. DBI version 1.650 sets a hard limit of 99,999 placeholders.
When was the CVE record for CVE-2026-14739 published?
The CVE record for CVE-2026-14739 was published on July 7, 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 October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-14739 actively exploited?
CVE-2026-14739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14739?
CVE-2026-14739 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14739?
A fix for CVE-2026-14739 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 version 1.650 or later." The vendor advisories EchelonGraph has for CVE-2026-14739 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14739?

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