CVE-2026-14740

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment.

The preparse method normalises SQL and removes comments. When the SQL starts with a comment line, the deletion of that line during normalisation led to an out-of-bounds read by one byte. The result is a fault on memory-hardened builds and nondeterministic newline retention on normal builds.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Aug 30, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

oss-security - CVE-2026-14740: DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment

http://www.openwall.com/lists/oss-security/2026/07/07/17
generic🟡 PoC Available

ChangeLog - metacpan.org

https://metacpan.org/release/HMBRAND/DBI-1.650/changes
github Patch Available

DBI: one-byte out-of-bounds read in preparse() when an initial SQL line comment is deleted · Advisory · perl5-dbi/dbi · GitHub

https://github.com/perl5-dbi/dbi/security/advisories/GHSA-35f4-f8m9-w8xg

Vendor Advisories for CVE-2026-14740(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
perl-dbi1.651-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.643-3 ... 1.651-1 (10 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.643-4 ... 1.651-1 (9 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.647-1 ... 1.651-1 (6 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.647-1, 1.648-1, 1.649-11.650-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 179× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 259 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-14740?
CVE-2026-14740 is a critical vulnerability published on July 7, 2026. DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment. The preparse method normalises SQL and removes comments. When the SQL starts with a comment line, the deletion of that line during normalisation led to an out-of-bounds read by one byte.…
When was CVE-2026-14740 disclosed?
CVE-2026-14740 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14740 actively exploited?
CVE-2026-14740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.4% of all scored CVEs.
What is the CVSS score of CVE-2026-14740?
CVE-2026-14740 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14740?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14740, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14740?

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