DbiApplication · Perl
CVE-2026-14739
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDBI 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.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDBI versions before 1.650 for Perl contain a heap overflow vulnerability when preparsing SQL statements containing an extreme number of placeholders. The prior fix for CVE-2026-10879 allocated insufficient memory, allowing approximately 1.2-million placeholders to trigger the overflow. Version 1.650 implements a hard limit of 99,999 placeholders to prevent this.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DbiApplication
< 1.650CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed DBI versionRun `perl -MDBI -e 'print $DBI::VERSION'` or check the version in your local Perl library (e.g., `perl -e 'use DBI; print $DBI::VERSION;'`)Affected if The version returned is less than 1.650 (e.g., 1.649, 1.640, etc.)
-
Verify DBI module file versionLocate the DBI.pm file (typically in `site/lib/DBI.pm` or `lib/DBI.pm` under your Perl prefix) and check its $VERSION variable: `perl -MExtUtils::MakeMaker -e 'print MM->new({VERSION=>1})->parse_version("$(find $(perl -e 'print join(":",@INC)' | tr ":" " ") -name DBI.pm -print -quit)")' 2>/dev/null || perl -l -e 'require "$(find $(perl -e 'print join(":",@INC)' | tr ":" " ") -name DBI.pm -print -quit)"; print $DBI::VERSION'Affected if The version parsed from the DBI.pm file is below 1.650
-
Identify SQL placeholder usage in your applicationSearch your application codebase for DBI prepare/execute statements with placeholders: grep -rE '(prepare|execute|bind_param|bind_columns)' --include='*.pl' --include='*.pm' --include='*.pm' . 2>/dev/null | grep -E '\?' or analyze database query logs for SQL statements containing multiple `?` placeholdersAffected if Your application uses DBI to prepare or execute SQL statements with placeholders and the DBI version is below 1.650
-
Check for dynamic placeholder generation from untrusted inputReview code paths where the number of placeholders could be controlled by user input (e.g., WHERE IN (?) expansions, dynamic array binding). Search for patterns like `join(',', ('?') x scalar @array)` or any logic that expands placeholders based on input sizeAffected if Your code constructs SQL with placeholder counts derived from user-controlled input without explicit limits, and DBI version is below 1.650
You are affected if your installed DBI version is below 1.650 and your application uses DBI to prepare SQL statements containing placeholders, particularly where placeholder count could be influenced by external input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.650
Upgrade to DBI version 1.650 or later, which enforces a 99,999 placeholder limit to prevent heap overflow. Test database operations after the upgrade to ensure compatibility.
DBI 1.650
- Check current DBI version: perl -MDBI -e 'print $DBI::VERSION'
- Upgrade DBI to version 1.650 or later using CPAN: cpan -i DBI
- Or use system package manager if available (e.g., apt-get install libdbi-perl on Debian/Ubuntu)
- Verify upgrade: perl -MDBI -e 'print $DBI::VERSION'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Dbi
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14739 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data