CVE-2026-60082
Perl DBI memory corruption in prepare can lead to remote code execution.
Is CVE-2026-60082 being exploited?
Not confirmed. CVE-2026-60082 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-60082?
CVE-2026-60082 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-60082?
Yes. A fix has been recorded for CVE-2026-60082. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-60082 affect?
CVE-2026-60082 affects Perl DBI < 1.651, Perl applications using DBI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-60082?
Upgrade DBI to >=1.651 and validate/sanitize statement metadata and rows
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds negative index read in DBI prepare can cause memory corruption and enable remote code execution when attacker controls metadata/rows.
Immediate action required
- affected< 1.651
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.