CVE-2026-73194: CWE-1284 Improper Validation of Specified Quantity in Input
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, ":p%d", 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.
AI Analysis
Technical Summary
In Perl DBI versions prior to 1.652, the preparse function reserves seven output bytes per input byte for placeholder expansion. The numeric placeholder ':N' is parsed using atoi without range checking, allowing a large value such as ':2147483648' to wrap to a negative integer (-2147483648). This negative binder counter causes subsequent '?' placeholders to expand into strings that exceed the allocated buffer size, resulting in a heap out-of-bounds write. The vulnerability affects callers that preparse untrusted statements into ':pN' style placeholders. Other return styles like '?' and '%s' that compare parsed numbers against expected sequences are not affected.
Potential Impact
This vulnerability can lead to heap corruption due to out-of-bounds writes, potentially causing crashes or memory corruption in applications using affected DBI versions. There is no indication of known exploits in the wild. The impact is limited to scenarios where untrusted input is parsed into ':pN' style placeholders.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid preparsing untrusted statements into ':pN' style placeholders in affected DBI versions. Monitor vendor channels for updates and apply official patches once released.
CVE-2026-73194: CWE-1284 Improper Validation of Specified Quantity in Input
Description
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, ":p%d", 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Perl DBI versions prior to 1.652, the preparse function reserves seven output bytes per input byte for placeholder expansion. The numeric placeholder ':N' is parsed using atoi without range checking, allowing a large value such as ':2147483648' to wrap to a negative integer (-2147483648). This negative binder counter causes subsequent '?' placeholders to expand into strings that exceed the allocated buffer size, resulting in a heap out-of-bounds write. The vulnerability affects callers that preparse untrusted statements into ':pN' style placeholders. Other return styles like '?' and '%s' that compare parsed numbers against expected sequences are not affected.
Potential Impact
This vulnerability can lead to heap corruption due to out-of-bounds writes, potentially causing crashes or memory corruption in applications using affected DBI versions. There is no indication of known exploits in the wild. The impact is limited to scenarios where untrusted input is parsed into ':pN' style placeholders.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid preparsing untrusted statements into ':pN' style placeholders in affected DBI versions. Monitor vendor channels for updates and apply official patches once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-08-11T11:58:19.137Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a805affbf8831d5390c8135
Added to database: 08/15/2026, 12:26:39 UTC
Last enriched: 08/15/2026, 12:43:20 UTC
Last updated: 08/15/2026, 13:57:15 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.