DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment
CVE-2026-14740 is fixed in 5 products on 1 platform, first by OPENSUSE-SU-2026:21293-1, released July 10, 2026. It is not reported as exploited. Patch Radar priority: High.
DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment. The preparse method normalises SQL and removes comments. When the SQL starts with a comment line, the deletion of that line during normalisation led to an out-of-bounds read by one byte. The result is a fault on memory-hardened builds and nondeterministic newline retention on normal builds.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libdbi-perl · Debian 12.15 (bookworm) | 1.643-4+deb12u2 | DEBIAN-CVE-2026-14740 | Jul 11, 2026 |
| libdbi-perl · Debian 13.5 (trixie) | 1.652-2~deb13u1 | DEBIAN-CVE-2026-14740 | Jul 11, 2026 |
| libdbi-perl · Debian 14 | 1.650-1 | DEBIAN-CVE-2026-14740 | Jul 11, 2026 |
| perl-DBI · amzn 2023 | 1.650-1.amzn2023.0.1 | ALAS2023-2026-1982 | Jul 20, 2026 |
| perl-DBI · opensuse-leap 16.0 | 1.647.0-160000.4.1 | OPENSUSE-SU-2026:21293-1 | Jul 10, 2026 |
| perl-DBI · sles 15.6 | 1.647.0-150600.12.18.1 | SUSE-SU-2026:3415-1 | Jul 30, 2026 |
| perl-DBI · sles 15.7 | 1.647.0-150600.12.18.1 | SUSE-SU-2026:3415-1 | Jul 30, 2026 |
| perl-DBI · sles 16.0 | 1.647.0-160000.4.1 | SUSE-SU-2026:22623-1 | Jul 10, 2026 |
| perl-DBI-debuginfo · amzn 2023 | 1.650-1.amzn2023.0.1 | ALAS2023-2026-1982 | Jul 20, 2026 |
| perl-DBI-debugsource · amzn 2023 | 1.650-1.amzn2023.0.1 | ALAS2023-2026-1982 | Jul 20, 2026 |
| perl-DBI-tests · amzn 2023 | 1.650-1.amzn2023.0.1 | ALAS2023-2026-1982 | Jul 20, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.