Resource exhaustion in Elixir-Ecto Ecto
CVE-2026-118391
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.
Published · last modified .
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- EEF CNA record for CVE-2026-118391 (related)
- Ecto.Query.API.json_extract_path/2 (technical-description)
- Ecto.Query.API.splice/1 (technical-description)
- Introducing commit cb2f039 in elixir-ecto/ecto (related)
- Do not cache queries with interpolated JSON paths, splices, and constants (main) (patch)
- Add splice to fragment (#4228), v3.11.0 (related)
- Fix commit eef014a in elixir-ecto/ecto (patch)
- String interpolation will grow cached unboundedly (#1031) (related)
- Should we allow disabling of Ecto cache on specific queries? (#4470) (related)
- GHSA-cxjx-vmm2-qr8r (vendor-advisory)