CVE-2026-60082 is an out-of-bounds read vulnerability in Perl DBI versions before 1.651. DBI failed to enforce consistency between a statement handle and its source row. If a statement handle has no fields while the corresponding source row is non-empty, an internal row-buffer helper reads from a negative array index. The condition can be triggered by supplying inconsistent metadata and rows to the prepare method.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability affecting the FreeBSD p5-DBI package, addressed in DBI releases 1.650 through 1.654. The content does not provide vulnerability-specific technical details.
A vulnerability referenced in the Huawei EulerOS SA-2026-3605 security advisory; the content provides no technical details.
A vulnerability addressed by Huawei EulerOS security advisory EulerOS_SA-2026-3659; no technical vulnerability details are provided in the content.
A vulnerability addressed by the EulerOS_SA-2026-3291 security advisory; no technical vulnerability description is provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.