# CVE-2026-60082: DBI versions before 1.651 for Perl do not enforce statement handle consistency with the row

> A flaw in the Perl DBI library allows a denial of service via negative array index read when inconsistent metadata is supplied.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALPINE-CVE-2026-60082, AZL-92421, BELL-CVE-2026-60082, DEBIAN-CVE-2026-60082, ECHO-5b7b-64b3-88c0, GHSA-rwhc-hhmv-cjvg, MINI-vhfr-h794-68xp, UBUNTU-CVE-2026-60082

## What is CVE-2026-60082?

CVE-2026-60082 is a critical vulnerability in HMBRAND DBI, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DBI versions before 1.651 for Perl do not enforce statement handle consistency with the row.

When the statement handle had no fields but the source row was non-empty, the internal row-buffer helper would read from a negative array index.

This could be triggered by a caller supplying inconsistent metadata and rows to the prepare method.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-60082?


## How do I fix CVE-2026-60082?

Upgrade to a fixed version.

## Is CVE-2026-60082 being exploited?

There is no known exploitation of CVE-2026-60082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60082 and fix it if it is affected.

What it is: CVE-2026-60082 is a critical vulnerability in HMBRAND DBI, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60082 in the wild and no public exploit code.

Affected product: HMBRAND DBI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60082/ (Markdown: https://insights.sbomify.com/CVE-2026-60082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60082
- OSV: https://osv.dev/vulnerability/CVE-2026-60082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60082/
Summaries are generated and may contain mistakes; the official description above is the record.