dbcve.org
DbiApplication · Perl

CVE-2026-10879

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 1.648 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
DBI versions before 1.648 for Perl have a heap overflow when preparsing SQL statements with more than 9 binders. The preparse method expands SQL placeholder characters to numbered binders of the form :pN, but only allocates three characters per binder in the buffer. Placeholders 10-99 require four characters, 100-999 require five characters, et cetera.

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 confidence

Heap buffer overflow in DBI Perl's SQL statement preparsing function. The code allocates only 3 characters per placeholder when expanding SQL placeholders to :pN format, but placeholders 10-99 require 4 characters and 100-999 require 5 characters. When more than 9 binders are present, this undersized buffer allocation causes heap memory corruption leading to potential arbitrary code execution.

MitigationUpgrade DBI to version 1.648 or later which contains the corrected buffer allocation logic for placeholder expansion.

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
Affected:< 1.648

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify DBI installation and version
    Run 'perl -MDBI -e "print $DBI::VERSION"' or check the DBI.pm file in your Perl @INC path for the $VERSION variable
    Affected if The reported version is lower than 1.648 (e.g., 1.647, 1.643, etc.)
  2. Verify the vulnerable code path is reachable
    Review application code to confirm it uses DBI's prepare(), do(), or other statement preparation methods that trigger placeholder expansion
    Affected if The application uses DBI statement preparation with SQL containing placeholders
  3. Identify statements with more than 9 placeholders
    Audit SQL statements or query logs to find statements containing more than 9 placeholder markers (?, :name, or :pN format) in a single query
    Affected if Any SQL statement processed by DBI contains 10 or more placeholders (the buffer overflow triggers with 10-99 placeholders needing 4 chars, and 100-999 needing 5 chars)
  4. Check for heap corruption indicators
    Run the application under memory debugging tools (e.g., Valgrind, AddressSanitizer) or monitor for crashes/heap metadata corruption in logs when processing multi-placeholder queries
    Affected if Heap corruption, crashes, or unexpected memory behavior occurs when processing queries with 10+ placeholders

Your environment is affected if DBI version is below 1.648 AND your application processes SQL statements containing 10 or more placeholders through DBI's prepare or similar methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.648 or later
Fixed in 1.648
Vendor patch github.com →
Interim mitigation

Upgrade DBI to version 1.648 or later which contains the corrected buffer allocation logic for placeholder expansion.

Recommended fix High confidence

1.648

  1. Check current DBI version: perl -MDBI -e 'print $DBI::VERSION'
  2. Upgrade DBI via CPAN: cpan DBI
  3. Or using cpanm: cpanm DBI
  4. Or via system package manager (e.g., apt-get install libdbi-perl on Debian/Ubuntu)
  5. Verify upgrade successful: perl -MDBI -e 'print $DBI::VERSION' and confirm version is 1.648 or higher

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
9.0 hours of engineering $1,540
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10879 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10879 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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