What’s Vulnerable › Vulnerabilities

CVE-2026-66838: SQL injection via the :comment option in Postgrex.stream/4

• Severity: high (CVSS 8.2 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-08-07 · updated 2026-10-24
• Weakness: CWE-89

Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in elixir-ecto postgrex allows SQL Injection via the :comment option of Postgrex.stream/4. An attacker who can influence that value can close the comment delimiter with */ and extend the streamed statement with their own clauses, which execute under the connection's role. Ecto exposes the same option through Ecto.Repo.stream/2. Postgrex appends the comment by concatenating it into the statement text sent in the Parse message, without escaping or rejecting */. The option is validated by comment_not_present!/1 at every other execution point; stream/4 never calls it. Because Parse accepts a single command, the injection is confined to the streamed statement and further statements cannot be chained. This issue affects postgrex: from 0.19.3 before 0.22.4.

Affected products

• elixir-ecto postgrex: from 0.19.3 before 0.22.4 — fixed in 0.22.4

How to fix

Upgrade to a fixed version: elixir-ecto postgrex 0.22.4. Check the vendor advisory for mitigations.

References

• https://cna.erlef.org/cves/CVE-2026-66838.html
• https://github.com/elixir-ecto/ecto/security/advisories/GHSA-3gww-3f36-2388
• https://github.com/elixir-ecto/postgrex/commit/4011be852c99dc61ddb98cb01aa41e8775a0e3dd
• https://github.com/elixir-ecto/postgrex/commit/e1ecba618ddea4cee2556bd6ad9b6285e05f9d3c
• https://osv.dev/vulnerability/EEF-CVE-2026-66838
• https://github.com/elixir-ecto/ecto/security/advisories/GHSA-3gww-3f36-2388

Get alerted when CVE-2026-66838 or the next vulnerability affects your stack