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 67% 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 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)
EPSS
32.9%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Jul 8, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 46× in last 7d / 54× 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.

  1. 2026-07-15 22:38 UTCEG score recompute
  2. 2026-07-15 22:38 UTCVendor advisory
  3. 2026-07-15 18:16 UTCEG score recompute
  4. 2026-07-15 18:16 UTCVendor advisory
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 13:54 UTCEG score recompute
  7. 2026-07-15 13:54 UTCVendor advisory
  8. 2026-07-15 09:32 UTCEG score recompute
  9. 2026-07-15 09:32 UTCVendor advisory
  10. 2026-07-15 05:07 UTCEG score recompute
  11. 2026-07-15 05:07 UTCVendor advisory
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 00:45 UTCEG score recompute
  14. 2026-07-15 00:45 UTCVendor advisory
  15. 2026-07-14 20:22 UTCEG score recompute
  16. 2026-07-14 20:22 UTCVendor advisory
  17. 2026-07-14 16:00 UTCEG score recompute
  18. 2026-07-14 16:00 UTCVendor advisory
  19. 2026-07-14 11:38 UTCEG score recompute
  20. 2026-07-14 11:38 UTCVendor advisory
  21. 2026-07-14 07:16 UTCEG score recompute
  22. 2026-07-14 07:16 UTCVendor advisory
  23. 2026-07-14 02:54 UTCEG score recompute
  24. 2026-07-14 02:54 UTCVendor advisory
  25. 2026-07-13 22:33 UTCEG score recompute
Show 29 more
  1. 2026-07-13 22:30 UTCEPSS rescore
  2. 2026-07-13 18:10 UTCEG score recompute
  3. 2026-07-13 13:49 UTCEG score recompute
  4. 2026-07-13 09:27 UTCEG score recompute
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-13 05:05 UTCEG score recompute
  7. 2026-07-13 00:42 UTCEG score recompute
  8. 2026-07-12 20:18 UTCEG score recompute
  9. 2026-07-12 15:57 UTCEG score recompute
  10. 2026-07-12 11:35 UTCEG score recompute
  11. 2026-07-12 07:14 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 02:51 UTCEG score recompute
  14. 2026-07-11 22:29 UTCEG score recompute
  15. 2026-07-11 18:08 UTCEG score recompute
  16. 2026-07-11 13:47 UTCEG score recompute
  17. 2026-07-11 09:26 UTCEG score recompute
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 05:05 UTCEG score recompute
  20. 2026-07-11 00:44 UTCEG score recompute 9.10
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 15:15 UTCEPSS rescore
  24. 2026-07-08 14:05 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  25. 2026-07-08 02:31 UTCNVD update
  26. 2026-07-08 00:55 UTCMITRE cvelistV5
  27. 2026-07-08 00:21 UTCNVD update
  28. 2026-07-07 22:32 UTCEG score recompute
  29. 2026-07-07 22:32 UTCMITRE cvelistV5first tracked

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 32.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.