Bug 2486734 (CVE-2026-9698) - CVE-2026-9698 DBI: DBI: Buffer overflow in error handling can lead to arbitrary code execution
Summary: CVE-2026-9698 DBI: DBI: Buffer overflow in error handling can lead to arbitra...
Keywords:
Status: NEW
Alias: CVE-2026-9698
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2488910
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-09 08:01 UTC by OSIDB Bzimport
Modified: 2026-07-13 12:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:38512 0 None None None 2026-07-13 08:43:12 UTC
Red Hat Product Errata RHSA-2026:38513 0 None None None 2026-07-13 04:21:41 UTC
Red Hat Product Errata RHSA-2026:38901 0 None None None 2026-07-13 12:55:49 UTC

Description OSIDB Bzimport 2026-06-09 08:01:15 UTC
DBI versions before 1.648 for Perl saved errors in a limited-sized buffer.

Error messages that were returned when RaiseError, PrintError or HandleError were set were written to a 200-byte buffer without a length limit.

Attackers that can influence the error text in an application can trigger a buffer overflow.

Comment 2 errata-xmlrpc 2026-07-13 04:21:40 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:38513 https://access.redhat.com/errata/RHSA-2026:38513

Comment 3 errata-xmlrpc 2026-07-13 08:43:11 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:38512 https://access.redhat.com/errata/RHSA-2026:38512

Comment 4 errata-xmlrpc 2026-07-13 12:55:48 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:38901 https://access.redhat.com/errata/RHSA-2026:38901


Note You need to log in before you can comment on or make changes to this bug.