CVE-2026-73194
Heap out-of-bounds write via unvalidated numeric placeholder in Perl DBI preparse.
Is CVE-2026-73194 being exploited?
Not confirmed. CVE-2026-73194 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.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-73194?
CVE-2026-73194 is rated Critical with a CVSS score of 9.1. 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-73194?
Yes. A fix has been recorded for CVE-2026-73194. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73194 affect?
CVE-2026-73194 affects Perl DBI versions < 1.652, Applications that preparse SQL into ':pN' placeholders. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73194?
Upgrade Perl DBI to >=1.652 and avoid preparsing untrusted statements.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker supplying a crafted ':N' placeholder in prepared statements can trigger heap OOB writes, causing crashes or possible arbitrary code execution when parsing untrusted input.
Immediate action required