EUVD-2026-43728Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploitation requires the victim to parse an attacker-supplied profile dump file, so AV:L and UI:R; impact is availability-only memory exhaustion, hence C:N/I:N/A:H.
Primary rating from Vendor (CPANSec).
CVSS VectorVendor: CPANSec
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Lifecycle Timeline
5DescriptionCVE.org
DBI::ProfileData versions before 1.651 for Perl do not limit the path index.
The path index column of profile dump files is used to allocate an array of data for the parser. An unbounded value allows an attacker to specify a large index and consume available memory.
AnalysisAI
Memory-exhaustion denial of service in the DBI::ProfileData module (bundled with Perl DBI) before version 1.651 allows an attacker who supplies a crafted profile dump file to force the parser into allocating an oversized array. Because the path-index column is read directly from an untrusted file and used to size an in-memory array, a tiny malicious file can amplify into large memory consumption (CWE-770). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that a victim system parse an attacker-controlled DBI profile dump file through DBI::ProfileData (typically via the dbiprof frontend or DBI::Profile-based tooling) at a version before 1.651. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) rates this a network, no-auth, availability-only issue. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a small DBI profile dump file containing a path-index line with an enormous integer value and gets it processed by a victim's dbiprof/DBI::ProfileData parser (for example, an automated profiling pipeline that ingests uploaded or shared dump files). When parsed, the oversized index causes a large sparse array allocation and repeated copies, exhausting available memory and denying service. … |
| Remediation | Vendor-released patch: upgrade Perl DBI to version 1.651 or later, which bounds the profile-file path index (see the GHSA-ww49-w4mv-jrr4 advisory and the DBI-1.651 changelog at https://metacpan.org/release/HMBRAND/DBI-1.651/changes). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all systems running Perl DBI versions prior to 1.651 and determine whether the ProfileData module is actively used in production applications. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Heap out-of-bounds write in the Perl DBI database-interface module before version 1.650 occurs when DBI preparses a SQL
Heap buffer overflow in the Perl DBI module versions before 1.648 occurs when the preparse() function processes SQL stat
Stack-based buffer overflow in Perl DBI module versions prior to 1.648 allows attackers who can influence database error
Incorrect WHERE-clause evaluation in Perl's DBI::SQL::Nano (versions 1.42 up to 1.651) causes text-based '<=' and '>=' c
Out-of-bounds read in the Perl DBI module's preparse() SQL-normalisation routine allows an attacker who controls SQL pas
Out-of-bounds read in the Perl DBI (Database Independent Interface) module before version 1.651 lets a caller trigger a
DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile. When a string is ass
Same technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today