Memory corruption via undersized SQL preparse buffer
Published Jul 7, 2026 · Updated Jul 7, 2026
Heap overflow in Perl DBI before 1.650 allows remote attackers to corrupt memory by preparing SQL with extreme placeholder counts. The DBI.xs preparse routine allocates output at six times the SQL length, but converting roughly 1.2 million question-mark placeholders to expanding :pN names exceeds that heap buffer. Reachability depends on an application passing attacker-controlled SQL to DBI; the resulting memory corruption can affect process confidentiality, integrity, and availability.
Summary
What happened
Heap overflow in Perl DBI before 1.650 allows remote attackers to corrupt memory by preparing SQL with extreme placeholder counts. The DBI.xs preparse routine allocates output at six times the SQL length, but converting roughly 1.2 million question-mark placeholders to expanding :pN names exceeds that heap buffer. Reachability depends on an application passing attacker-controlled SQL to DBI; the resulting memory corruption can affect process confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-14739
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Vendor
- Perl DBI
- Product
- DBI
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Jul 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.650
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo