<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-07T18:39:25.538389+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-121009</id>
    <title>CVE-2026-121009 — SQL::Abstract versions from 1.90_01 before 2.000001_04 for Perl skip the injection_guard check for function names given…</title>
    <updated>2026-11-07T18:39:25.539349+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> SQL-Abstract</p>
<p>SQL::Abstract versions from 1.90_01 before 2.000001_04 for Perl skip the injection_guard check for function names given with -func.</p>
<p>injection_guard is documented to apply to every function name, but only the { -name =&gt; ... } shorthand goes through it. The explicit { -func =&gt; [ $name, ... ] } form puts $name into the SQL unchecked.</p>
<p>An application that relies on injection_guard to reject an untrusted function name passed with -func allows SQL injection.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-121009"/>
  </entry>
</feed>
