DBD::File versions before 1.651 for Perl do not ensure the table file is not a symlink to an untrusted location
CVE-2026-15392 is fixed in 5 products on 1 platform, first by DEBIAN-CVE-2026-15392, released July 18, 2026. It is not reported as exploited. Patch Radar priority: High.
DBD::File versions before 1.651 for Perl do not ensure the table file is not a symlink to an untrusted location. The complete_table_name method builds the absolute table file path without checking whether the file is a symbolic link. A link inside the data directory can point to a table file at any path outside of the configured f_dir and f_dir_search directories. Callers of file-based drivers can read or write files outside of the data directory.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libdbi-perl · Debian 12.15 (bookworm) | 1.643-4+deb12u2 | DEBIAN-CVE-2026-15392 | Jul 18, 2026 |
| libdbi-perl · Debian 13.5 (trixie) | 1.652-2~deb13u1 | DEBIAN-CVE-2026-15392 | Jul 18, 2026 |
| libdbi-perl · Debian 14 | 1.651-1 | DEBIAN-CVE-2026-15392 | Jul 18, 2026 |
| perl-DBI · amzn 2023 | 1.651-1.amzn2023.0.1 | ALAS2023-2026-2006 | Aug 3, 2026 |
| perl-DBI · opensuse-leap 16.0 | 1.647.0-160000.5.1 | OPENSUSE-SU-2026:21412-1 | Jul 22, 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.5.1 | SUSE-SU-2026:22845-1 | Jul 22, 2026 |
| perl-DBI-debuginfo · amzn 2023 | 1.651-1.amzn2023.0.1 | ALAS2023-2026-2006 | Aug 3, 2026 |
| perl-DBI-debugsource · amzn 2023 | 1.651-1.amzn2023.0.1 | ALAS2023-2026-2006 | Aug 3, 2026 |
| perl-DBI-tests · amzn 2023 | 1.651-1.amzn2023.0.1 | ALAS2023-2026-2006 | Aug 3, 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.