Skip to content
Noroxi
NVD / CVE Program· CNA CPANSec

CVE-2026-73194: 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

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: perl-DBI (AlmaLinux:10) 1.643-26.el10_2.6; perl-DBI (AlmaLinux:8) 1.641-10.module_el8.10.0+4282+4ee1dbd0, 1.641-3.el8_10; perl-DBI (AlmaLinux:9) 1.643-9.el9_8.6.

Low priority for now. Upgrade to perl-DBI (AlmaLinux:10) 1.643-26.el10_2.6; perl-DBI (AlmaLinux:8) 1.641-10.module_el8.10.0+4282+4ee1dbd0, 1.641-3.el8_10; perl-DBI (AlmaLinux:9) 1.643-9.el9_8.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 28, 2026
EPSS
0.4% · 42th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-73194

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (CPANSec). Independent of NVD's CPE analysis and usually ahead of it.

  • cpan.org/modules DBI

    • before 1.652affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10perl-DBIbefore 1.643-26.el10_2.61.643-26.el10_2.6
AlmaLinux:8perl-DBIbefore 1.641-10.module_el8.10.0+4282+4ee1dbd01.641-10.module_el8.10.0+4282+4ee1dbd0
AlmaLinux:8perl-DBIbefore 1.641-3.el8_101.641-3.el8_10
AlmaLinux:9perl-DBIbefore 1.643-9.el9_8.61.643-9.el9_8.6
Debian:12libdbi-perlbefore 1.643-4+deb12u21.643-4+deb12u2
Debian:13libdbi-perlbefore 1.652-2~deb13u11.652-2~deb13u1
Debian:14libdbi-perlbefore 1.652-11.652-1
openSUSE:Tumbleweedperl-DBIbefore 1.653.0-1.11.653.0-1.1
Red Hat:enterprise_linux:10.2perl-DBIbefore 0:1.643-26.el10_2.60:1.643-26.el10_2.6
Red Hat:enterprise_linux:10.2perl-DBI-debuginfobefore 0:1.643-26.el10_2.60:1.643-26.el10_2.6
Red Hat:enterprise_linux:10.2perl-DBI-debugsourcebefore 0:1.643-26.el10_2.60:1.643-26.el10_2.6
Red Hat:enterprise_linux:8::appstreamperl-DBIbefore 0:1.641-10.module+el8.10.0+24875+bc9629740:1.641-10.module+el8.10.0+24875+bc962974
Red Hat:enterprise_linux:8::appstreamperl-DBI-debuginfobefore 0:1.641-10.module+el8.10.0+24875+bc9629740:1.641-10.module+el8.10.0+24875+bc962974
Red Hat:enterprise_linux:8::appstreamperl-DBI-debugsourcebefore 0:1.641-10.module+el8.10.0+24875+bc9629740:1.641-10.module+el8.10.0+24875+bc962974
Red Hat:enterprise_linux:8::baseosperl-DBIbefore 0:1.641-3.el8_100:1.641-3.el8_10
Red Hat:enterprise_linux:8::baseosperl-DBI-debuginfobefore 0:1.641-3.el8_100:1.641-3.el8_10
Red Hat:enterprise_linux:8::baseosperl-DBI-debugsourcebefore 0:1.641-3.el8_100:1.641-3.el8_10
Red Hat:enterprise_linux:9::appstreamperl-DBIbefore 0:1.643-9.el9_8.60:1.643-9.el9_8.6
Red Hat:enterprise_linux:9::appstreamperl-DBI-debuginfobefore 0:1.643-9.el9_8.60:1.643-9.el9_8.6
Red Hat:enterprise_linux:9::appstreamperl-DBI-debugsourcebefore 0:1.643-9.el9_8.60:1.643-9.el9_8.6
Rocky Linux:10perl-DBIbefore 0:1.643-26.el10_2.60:1.643-26.el10_2.6
Rocky Linux:8perl-DBIbefore 0:1.641-10.module+el8.10.0+40328+bc0902410:1.641-10.module+el8.10.0+40328+bc090241
Rocky Linux:8perl-DBIbefore 0:1.641-10.module+el8.10.0+40328+3ea703670:1.641-10.module+el8.10.0+40328+3ea70367
Rocky Linux:8perl-DBIbefore 0:1.641-10.module+el8.10.0+40328+0878361a0:1.641-10.module+el8.10.0+40328+0878361a

+3

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:perl-DBI1.641-10.module_el8.10.0+4282+4ee1dbd0 · AlmaLinux:8Package registry (OSV)
debian:libdbi-perl1.643-4+deb12u2 · Debian:12Package registry (OSV)
opensuse:perl-DBI1.653.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:perl-DBI0:1.641-10.module+el8.10.0+24875+bc962974 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:perl-DBI-debuginfo0:1.641-10.module+el8.10.0+24875+bc962974 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:perl-DBI-debugsource0:1.641-10.module+el8.10.0+24875+bc962974 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:perl-DBI0:1.641-10.module+el8.10.0+40328+bc090241 · Rocky Linux:8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records