Parsing-process crash via unbounded path index
Published Jul 14, 2026 · Updated Jul 14, 2026
Resource exhaustion in DBI::ProfileData before 1.651 allows attackers to crash the parsing process via a crafted profile dump file. In _read_body, an unbounded path index sets the size of @path, which is then joined and copied, amplifying a tiny input into heavy memory use. Exploitation requires the parser to process an untrusted dump crossing a file or workflow trust boundary; it does not affect normal database input or enable code execution.
Summary
What happened
Resource exhaustion in DBI::ProfileData before 1.651 allows attackers to crash the parsing process via a crafted profile dump file. In _read_body, an unbounded path index sets the size of @path, which is then joined and copied, amplifying a tiny input into heavy memory use. Exploitation requires the parser to process an untrusted dump crossing a file or workflow trust boundary; it does not affect normal database input or enable code execution.
The record
- CVE
- CVE-2026-60081
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Perl DBI
- Product
- DBI::ProfileData
- Classifications
- CWE-770, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.651
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream small-file memory-amplification proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo