CVE-2026-118391 · Package
NO FIX YET · SEE WHAT TO DO
Ecto caches prepared queries in an unbounded ETS table, and interpolated JSON keys or list lengths from request input create a new cache entry each time. An unauthenticated remote attacker can exhaust memory in the application and on the database server until processes restart.
first public Nov 4, 2026 · 1 source
Is this in your stack? Find out in 2 minutes.
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Applications built on Ecto from 3.4.0 before 3.14.3 that pass request-controlled JSON keys or list lengths into json_extract_path/2, field[^key] or splice/1 are exposed. Apps that only use fixed keys and fixed list shapes in queries are not affected by the request-driven growth. The sources do not say whether ecto_sql adds further exposure beyond the statement cache.
Not affected if ecto-before-3.4.0, no-request-controlled-json-keys, static-query-shapes
Who cares ecto, elixir, mysql, phoenix, postgres
grep ecto mix.lock in the Elixir project.json_extract_path/2, field[^key] or splice/1.3.14.3 or later (affected range from 3.4.0 before 3.14.3)Allocation of Resources Without Limits or Throttling vulnerability in elixir-ecto ecto allows an unauthenticated remote attacker to exhaust memory in the application and in the database server by sending requests with distinct JSON keys or list lengths where the application interpolates them into json_extract_path/2, field[^key] or splice/1. Ecto caches prepared queries per repository in an ETS table with no size limit and no eviction. Interpolated JSON path elements become part of the query expression instead of its parameters, and splice/1 expands into one placeholder per element, so every distinct key or list length creates a new cache entry. With ecto_sql each entry is also a new prepared statement on the database connection that runs it. None of this memory is released until the processes restart.
This issue affects ecto: from 3.4.0 before 3.14.3.
This page as .md · .json · in your agent: get_signal("CVE-2026-118391") · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.