CVE-2026-32687 SQL injection via channel name in Postgrex.Notifications.listen/3 and unlisten/3
Attackers can execute arbitrary SQL commands by injecting quotes into channel names in Postgrex notification functions, risking data modification or execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-32687?
CVE-2026-32687 is a high-severity SQL injection vulnerability in elixir-ecto postgrex, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in elixir-ecto postgrex ('Elixir.Postgrex.Notifications' module) allows SQL Injection.
The channel argument passed to 'Elixir.Postgrex.Notifications':listen/3 and 'Elixir.Postgrex.Notifications':unlisten/3 is interpolated directly into LISTEN "..." / UNLISTEN "..." SQL statements without escaping the " character. An attacker who can influence the channel name can inject a " 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.
This vulnerability is associated with program file lib/postgrex/notifications.ex and program routines 'Elixir.Postgrex.Notifications':listen/3, 'Elixir.Postgrex.Notifications':unlisten/3, 'Elixir.Postgrex.Notifications':handle_connect/1.
This issue affects postgrex: from 0.16.0 before 0.22.2.
Weakness: CWE-89
Which versions are affected by CVE-2026-32687?
3 open source packages ship an affected version, including postgrex. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
postgrex Hex | From 0.16.0 | 0.22.2 |
postgrex Hex | From 0.16.0 | 0.22.2 |
postgrex Hex | From 0.16.0 | 0.22.2 |
Products include Elixir-Ecto Postgrex.
How do I fix CVE-2026-32687?
Upgrade postgrex to 0.22.2 or later.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-32687 being exploited?
There is no known exploitation of CVE-2026-32687 in the wild and no public exploit code.
Other vulnerabilities in elixir-ecto postgrex
Sources
Also known as EEF-CVE-2026-32687, GHSA-r73h-97w8-m54h.