<?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://cve.radiocsirt.org</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>Mon, 12 Oct 2026 20:35:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32687 — SQL injection via channel name in Postgrex.Notifications.listen/3 and unlisten/3</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-32687</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elixir-ecto postgrex&lt;/p&gt;
&lt;p&gt;Improper Neutralization of Special Elements used in an SQL Command (&amp;#39;SQL Injection&amp;#39;) vulnerability in elixir-ecto postgrex (&amp;#39;Elixir.Postgrex.Notifications&amp;#39; module) allows SQL Injection.&lt;/p&gt;
&lt;p&gt;The channel argument passed to &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:listen/3 and &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:unlisten/3 is interpolated directly into LISTEN &amp;#34;...&amp;#34; / UNLISTEN &amp;#34;...&amp;#34; SQL statements without escaping the &amp;#34; character. An attacker who can influence the channel name can inject a &amp;#34; to break out of the quoted identifier and append arbitrary SQL. Because the notifications connection uses the PostgreSQL simple query protocol, multi-statement payloads are accepted, allowing DDL and DML commands to be chained (e.g. ; DROP TABLE ...; --). The same unsanitized interpolation also occurs in handle_connect/1 when replaying LISTEN commands after a reconnect.&lt;/p&gt;
&lt;p&gt;This vulnerability is associated with program file lib/postgrex/notifications.ex and program routines &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:listen/3, &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:unlisten/3, &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:handle_connect/1.&lt;/p&gt;
&lt;p&gt;This issue affects postgrex: from 0.16.0 before 0.22.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elixir-ecto postgrex&lt;/p&gt;
&lt;p&gt;Improper Neutralization of Special Elements used in an SQL Command (&amp;#39;SQL Injection&amp;#39;) vulnerability in elixir-ecto postgrex (&amp;#39;Elixir.Postgrex.Notifications&amp;#39; module) allows SQL Injection.&lt;/p&gt;
&lt;p&gt;The channel argument passed to &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:listen/3 and &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:unlisten/3 is interpolated directly into LISTEN &amp;#34;...&amp;#34; / UNLISTEN &amp;#34;...&amp;#34; SQL statements without escaping the &amp;#34; character. An attacker who can influence the channel name can inject a &amp;#34; to break out of the quoted identifier and append arbitrary SQL. Because the notifications connection uses the PostgreSQL simple query protocol, multi-statement payloads are accepted, allowing DDL and DML commands to be chained (e.g. ; DROP TABLE ...; --). The same unsanitized interpolation also occurs in handle_connect/1 when replaying LISTEN commands after a reconnect.&lt;/p&gt;
&lt;p&gt;This vulnerability is associated with program file lib/postgrex/notifications.ex and program routines &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:listen/3, &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:unlisten/3, &amp;#39;Elixir.Postgrex.Notifications&amp;#39;:handle_connect/1.&lt;/p&gt;
&lt;p&gt;This issue affects postgrex: from 0.16.0 before 0.22.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-32687</guid>
    </item>
  </channel>
</rss>
