<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 15:59:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-15043 — DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted &lt;= and &gt;= SQL operators on text</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-15043</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HMBRAND DBI::SQL::Nano&lt;/p&gt;
&lt;p&gt;DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted &amp;lt;= and &amp;gt;= SQL operators on text.&lt;/p&gt;
&lt;p&gt;DBI::SQL::Nano, DBI&amp;#39;s built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched method, &amp;lt;= was evaluated using Perl&amp;#39;s ge operator, and &amp;gt;= was evaluated using Perl&amp;#39;s le operator.&lt;/p&gt;
&lt;p&gt;SQL::Nano is the fallback query engine for DBI&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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 &amp;lt;=/&amp;gt;= comparison silently returns the wrong rows.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HMBRAND DBI::SQL::Nano&lt;/p&gt;
&lt;p&gt;DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted &amp;lt;= and &amp;gt;= SQL operators on text.&lt;/p&gt;
&lt;p&gt;DBI::SQL::Nano, DBI&amp;#39;s built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched method, &amp;lt;= was evaluated using Perl&amp;#39;s ge operator, and &amp;gt;= was evaluated using Perl&amp;#39;s le operator.&lt;/p&gt;
&lt;p&gt;SQL::Nano is the fallback query engine for DBI&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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 &amp;lt;=/&amp;gt;= comparison silently returns the wrong rows.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-15043</guid>
    </item>
  </channel>
</rss>
