Answer in brief
CVE-2026-58225 records a Low severity (CVSS 2.1) vulnerability in SQL injection via unescaped dollar-quote in Postgrex.Notifications reconnect replay causes notification denial of service. The current sources do not mark it as known exploited. The current feed maps elixir-ecto/elixir-ecto/postgrex (generic), elixir-ecto/postgrex (generic), elixir-ecto/postgrex (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps elixir-ecto/elixir-ecto/postgrex (generic), elixir-ecto/postgrex (generic), elixir-ecto/postgrex (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| elixir-ecto/elixir-ecto/postgrexgeneric | >=266b530faf9bde094e31e0e4ab851f933fadc0f5 <795c6062f62c4394272ff4b89170688857b4f841 | 795c6062f62c4394272ff4b89170688857b4f841 |
| elixir-ecto/postgrexgeneric | >=0.16.0 <0.22.3 | 0.22.3 |
| elixir-ecto/postgrexgeneric | >=266b530faf9bde094e31e0e4ab851f933fadc0f5 <795c6062f62c4394272ff4b89170688857b4f841 | 795c6062f62c4394272ff4b89170688857b4f841 |
Published upstream
Jul 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 10, 2026
SQL Injection vulnerability in elixir-ecto postgrex allows an attacker who can influence a LISTEN channel name to inject SQL into the reconnect replay query, causing a denial of service of the notification connection. Postgrex.Notifications sanitizes channel names with quote_channel/1, which doubles double quotes so the name is safe inside a double-quoted identifier. This protects the single-statement LISTEN and UNLISTEN paths. On every (re)connect, however, handle_connect/1 replays all registered channels at once by concatenating their LISTEN statements and wrapping them in a dollar-quoted anonymous code block (DO $$BEGIN ... END$$). quote_channel/1 does not escape the $$ dollar-quote delimiter that opens and closes this block. The listen/3 guards only reject null bytes and names longer than 63 bytes, so a channel name containing $$ passes validation unchanged. Once such a name is embedded, its $$ prematurely terminates the outer dollar-quoted string and PostgreSQL parses the remainder as additional top-level statements. Because handle_connect/1 runs on every (re)connect, the malformed replay query is rejected each time and the notification connection never re-establishes its subscriptions, silently dropping notifications for every channel sharing that connection. An application is affected when it passes untrusted input (for example a tenant or user identifier) as a channel name to Postgrex.Notifications.listen/3. The double-quote doubling prevents forming a fully valid injected statement, so arbitrary SQL execution is not possible, but the corrupted query reliably breaks the shared notification connection for all tenants, resulting in denial of service. This issue affects postgrex: from 0.16.0 before 0.22.3.
Quoted source text, attributed separately from HOL analysis.