CVE-2026-73193
Heap out-of-bounds write in DBI on 32-bit Perl via integer wraparound
Is CVE-2026-73193 being exploited?
Not confirmed. CVE-2026-73193 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-73193?
CVE-2026-73193 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73193?
Yes. A fix has been recorded for CVE-2026-73193. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73193 affect?
CVE-2026-73193 affects Perl DBI < 1.652 on 32-bit Perl builds, Perl applications using DBI preparse with untrusted input. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73193?
Upgrade DBI to >= 1.652, validate input sizes, prefer 64-bit Perl
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap OOB write of attacker-controlled bytes on 32-bit Perl; can crash or lead to code execution when parsing large untrusted statements.
Patch when possible