Code execution via unbounded error-prefix formatting
Published Jun 9, 2026 · Updated Jun 9, 2026
Stack buffer overflow in DBI before 1.648 allows remote attackers to execute code through attacker-influenced application errors. DBI.xs dispatch error handling uses unbounded sprintf to format a method prefix into a 200-byte stack buffer instead of allocating a size-matched Perl scalar. Reachability requires an application to return attacker-influenced errors with RaiseError, PrintError, or HandleError enabled; successful corruption can crash the process or execute code.
Summary
What happened
Stack buffer overflow in DBI before 1.648 allows remote attackers to execute code through attacker-influenced application errors. DBI.xs dispatch error handling uses unbounded sprintf to format a method prefix into a 200-byte stack buffer instead of allocating a size-matched Perl scalar. Reachability requires an application to return attacker-influenced errors with RaiseError, PrintError, or HandleError enabled; successful corruption can crash the process or execute code.
The record
- CVE
- CVE-2026-9698
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- DBI team
- Product
- DBI
- Classifications
- CWE-120, CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 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.648
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
No public exploit references are available in this record.
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