Use of Incorrect Operator Affecting perl-DBI package, versions <0:1.627-4.amzn2.0.6


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.67% (52nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2-PERLDBI-18523822
  • published5 Aug 2026
  • disclosed14 Jul 2026

Introduced: 14 Jul 2026

CVE-2026-15043  (opens in a new tab)
CWE-480  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 perl-DBI to version 0:1.627-4.amzn2.0.6 or higher.
This issue was patched in ALAS2-2026-3851.

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl-DBI package and not the perl-DBI package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted <= and >= SQL operators on text.

DBI::SQL::Nano, DBI's built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched method, <= was evaluated using Perl's ge operator, and >= was evaluated using Perl's le operator.

SQL::Nano is the fallback query engine for DBI's file-backed drivers (DBD::File, DBD::DBM, CSV-style drivers) whenever SQL::Statement is not installed, and is forced whenever DBI_SQL_NANO=1. Queries over such tables use these predicates directly.

The impact depends on the context. Where an application relies on a WHERE clause to filter file-backed data for policy or authorization, an inverted <=/>= comparison silently returns the wrong rows.

CVSS Base Scores

version 3.1