<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T01:27:37.294079+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-88816</id>
    <title>BELL-CVE-2026-88816</title>
    <updated>2026-11-21T01:27:37.300446+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: perl-dbi, Alpaquita:25: perl-dbi, Alpaquita:stream: perl-dbi</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-88816"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/brew-proteinortho-cve-2026-88816</id>
    <title>BREW-proteinortho-CVE-2026-88816 — DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName</title>
    <updated>2026-11-21T01:27:37.300532+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: proteinortho</p>
<p>DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName.</p>
<p>fetchrow_hashref uses the string pointer of the FetchHashKeyName attribute as the key name without stringifying it first. When FetchHashKeyName has been set to an integer (IV) or floating-point (NV) value, that pointer is invalid, so reading the key name triggers a segmentation fault.</p>
<p>This can be triggered with the following code:</p>
<p>my $dbh = DBI-&gt;connect( "dbi:ExampleP:", "", "",
       { RaiseError =&gt; 0, PrintError =&gt; 0 } );
   $dbh-&gt;{FetchHashKeyName} = 42;</p>
<p>my $sth = $dbh-&gt;prepare("select mode, size, name from .");
   $sth-&gt;execute;
   $sth-&gt;fetchrow_hashref;</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/brew-proteinortho-cve-2026-88816"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1333</id>
    <title>certfr-2026-avi-1333 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T01:27:37.300586+00:00</updated>
    <content>certfr-2026-avi-1333</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1333"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-4251</id>
    <title>OESA-2026-4251 — perl-DBI security update</title>
    <updated>2026-11-21T01:27:37.300612+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: perl-DBI</p>
<p>The DBI is the standard database interface module for Perl. It defines a set of methods, variables and conventions that provide a consistent database interface independent of the actual database being used. It is important to remember that the DBI is just an interface. The DBI is a layer of &amp;amp;quot;glue&amp;amp;quot; between an application and one or more database driver modules. It is the driver modules which do most of the real work. The DBI provides a standard interface and framework for the drivers to operate within.

Security Fix(es):</p>
<p>DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in sql_type_cast_svpv.</p>
<p>When casting to SQL_NUMERIC, sql_type_cast_svpv passes the string pointer and length of the SV to grok_number without stringifying it first. An integer (IV) or floating-point (NV) value has no valid string pointer, so grok_number reads from an invalid address, triggering a segmentation fault.</p>
<p>This is reachable in Perl using the sql_type_cast function:</p>
<p>my $num = 42;
  DBI::sql_type_cast( $num, DBI::SQL_NUMERIC, 0 );(CVE-2026-88815)</p>
<p>DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName.</p>
<p>fetchrow_hashref uses the string pointer of the FetchHashKeyName attribute as the key name without stringifying it first. When FetchHashKeyName has been set to an integer (IV) or floating-point (NV) value, that pointer is invalid, so reading the key name triggers a segmentation fault.</p>
<p>This can be triggered…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-4251"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-88816</id>
    <title>UBUNTU-CVE-2026-88816</title>
    <updated>2026-11-21T01:27:37.300709+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libdbi-perl, Ubuntu:Pro:16.04:LTS: libdbi-perl, Ubuntu:Pro:18.04:LTS: libdbi-perl, Ubuntu:Pro:20.04:LTS: libdbi-perl, Ubuntu:22.04:LTS: libdbi-perl, Ubuntu:24.04:LTS: libdbi-perl, Ubuntu:26.10: libdbi-perl, Ubuntu:26.04:LTS: libdbi-perl</p>
<p>DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName. fetchrow_hashref uses the string pointer of the FetchHashKeyName attribute as the key name without stringifying it first. When FetchHashKeyName has been set to an integer (IV) or floating-point (NV) value, that pointer is invalid, so reading the key name triggers a segmentation fault. This can be triggered with the following code:    my $dbh = DBI-&gt;connect( "dbi:ExampleP:", "", "",        { RaiseError =&gt; 0, PrintError =&gt; 0 } );    $dbh-&gt;{FetchHashKeyName} = 42;    my $sth = $dbh-&gt;prepare("select mode, size, name from .");    $sth-&gt;execute;    $sth-&gt;fetchrow_hashref;</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-88816"/>
  </entry>
</feed>
