<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-14T19:09:13.707164+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-44172</id>
    <title>CVE-2026-44172 — MariaDB: mysql_real_escape_string() incorrectly handled big5</title>
    <updated>2026-10-14T19:09:13.742743+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> MariaDB server, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Hardened Images, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9</p>
<p>MariaDB server is a community developed fork of MySQL server. In versions 3.3.18 and 3.4.8, an application that was taking non-validated user input, escaping it with mysql_real_escape_string() and sending it to the database using text protocol and big5 character set was vulnerable to SQL injections, even though mysql_real_escape_string() was supposed to prevent them. This issue has been patched in versions 3.3.19 and 3.4.9.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-44172"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-8536-1</id>
    <title>USN-8536-1 — mariadb vulnerabilities</title>
    <updated>2026-10-14T19:09:13.742875+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:26.04:LTS: mariadb</p>
<p>It was discovered that MariaDB did not properly validate parameters
supplied by a joiner node during a State Snapshot Transfer using the
mariabackup method. An attacker could possibly use this issue to execute
arbitrary shell commands on the donor node. (CVE-2026-44168)</p>
<p>It was discovered that MariaDB did not properly enforce the SHOW CREATE
ROUTINE privilege when a user obtained access to a stored routine via a
role. An authenticated user could possibly use this issue to obtain
sensitive information. (CVE-2026-44169)</p>
<p>It was discovered that MariaDB's mbstream utility did not properly validate
paths when unpacking archives. An attacker could possibly use this issue to
write files outside of the intended target directory. (CVE-2026-44171)</p>
<p>It was discovered that MariaDB's mysql_real_escape_string() function
incorrectly handled the big5 character set. An attacker could possibly use
this issue to perform SQL injection attacks. (CVE-2026-44172)</p>
<p>It was discovered that MariaDB did not properly check the FILE privilege
when the FROM clause of a SELECT ... INTO OUTFILE or SELECT ... INTO
DUMPFILE statement contained only subqueries. An authenticated user could
possibly use this issue to write files to unintended locations.
(CVE-2026-44173)</p>
<p>It was discovered that MariaDB did not properly validate parameters
supplied by a joiner node during a State Snapshot Transfer using the rsync
method. An attacker could possibly use this issue to execute arbitrary
shell commands on the donor nod…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-8536-1"/>
  </entry>
</feed>
