[From nobody Sat Aug 15 16:37:07 2026
Received: (at submit) by bugs.debian.org; 15 Aug 2026 14:38:28 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-10.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 NO_RELAYS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 150; neutral, 75; spammy,
 0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug,
 0.000-+--HTo:N*Debian
Return-path: &lt;carnil@debian.org&gt;
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;carnil@debian.org&gt;) id 1wvFWj-006qu0-2s
 for submit@bugs.debian.org; Sat, 15 Aug 2026 14:38:28 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: libdbi-perl: CVE-2026-73194
Message-ID: &lt;178680470492.1662134.6639049985467293130.reportbug@eldamar.lan&gt;
X-Mailer: reportbug 13.2.0+nmu1
Date: Sat, 15 Aug 2026 16:38:24 +0200
Delivered-To: submit@bugs.debian.org

Source: libdbi-perl
Version: 1.651-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team &lt;team@security.debian.org&gt;

Hi,

The following vulnerability was published for libdbi-perl.

CVE-2026-73194[0]:
| DBI versions before 1.652 for Perl allow a heap out-of-bounds write
| via an unvalidated numeric placeholder that sets the binder counter
| in preparse.  preparse reserves seven output bytes per input byte,
| the width of the longest ':p99999' expansion. The ':N' branch parses
| the number with `atoi(src)` and assigns it to the binder counter
| with no range check, so a statement containing ':2147483648' leaves
| the counter negative (-2147483648 with glibc, where atoi wraps).
| Each following '?' then expands through `sprintf(start, &quot;:p%d&quot;,
| idx++)` to ':p-2147483648', 14 bytes with the terminating NUL where
| the buffer budgets 7. The placeholder limit added in 1.650 tests the
| counter against 99,999, which a negative counter passes.  Any caller
| that preparses an untrusted statement into ':pN' style placeholders
| gets a heap out-of-bounds write that grows with the number of '?'
| marks following the poisoned placeholder. The '?' and '%s' return
| styles compare the parsed number against the expected sequence and
| error out, and are unaffected.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-73194
    https://www.cve.org/CVERecord?id=CVE-2026-73194
[1] https://lists.security.metacpan.org/cve-announce/msg/42707363/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]