LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-60082 affects Perl DBI before 1.651. A malformed internal data situation can make DBI read outside the expected row buffer. The rating is critical because the published CVSS indicates possible high confidentiality loss and high availability impact without authentication.

Executive priority

Treat as urgent for environments running Perl DBI, particularly internet-facing services. The risk is credible due to critical CVSS impact, but sources do not show confirmed active exploitation.

Technical view

The issue is a CWE-125 out-of-bounds read. If a statement handle has no fields while the source row is non-empty, DBI's internal row-buffer helper can read from a negative array index. Sources say this can be triggered through inconsistent metadata and rows supplied to prepare.

Likely exposure

Exposure is most likely in Perl applications or dependencies using DBI versions before 1.651, especially where application logic or test harnesses can pass inconsistent statement metadata and row data into DBI prepare handling.

Exploitation context

The CVE record has KEV marked false, and the provided sources do not state active exploitation. The published vector indicates network-reachable, unauthenticated, low-complexity impact, but the bundle does not provide real-world exploit evidence.

Researcher notes

Evidence supports DBI before 1.651 and a negative-index out-of-bounds read in row-buffer handling. The affected record also contains an unusual version entry, so validate exact downstream package status through vendor, MetaCPAN, and distribution advisories.

Mitigation direction

  • Upgrade DBI to version 1.651 or later.
  • Check vendor advisory and release notes before rollout.
  • Inventory Perl applications and dependencies using DBI.
  • Prioritize externally reachable services first.
  • Monitor vendor and distribution package advisories.

Validation and detection

  • Confirm installed DBI versions across production systems.
  • Review dependency lockfiles and OS package inventories.
  • Identify applications accepting untrusted database metadata paths.
  • Verify DBI 1.651 or later after remediation.
  • Track exceptions with compensating controls and owner.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-60082 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-60082Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HMBRANDDBIDBI, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.