CVE-2026-14740
One-byte OOB read in Perl DBI preparse when removing a leading SQL comment.
Is CVE-2026-14740 being exploited?
Not confirmed. CVE-2026-14740 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-14740?
CVE-2026-14740 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-14740?
Yes. A fix has been recorded for CVE-2026-14740. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14740 affect?
CVE-2026-14740 affects Perl DBI < 1.650, Perl applications using DBI preparse functionality. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14740?
Upgrade DBI to >=1.650 and validate SQL input; apply vendor patch immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted SQL with a leading comment can trigger a one-byte out-of-bounds read, causing process crash (DoS) and potential memory disclosure on some builds.
Immediate action required
- affected< 1.650
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.