Answer in brief
CVE-2026-118391 records a High severity (CVSS 8.9) vulnerability in Unbounded query cache growth from interpolated JSON paths and splice lists in Ecto. The current sources do not mark it as known exploited. The current feed maps elixir-ecto/ecto (generic), elixir-ecto/elixir-ecto/ecto (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 8.9. 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/ecto (generic), elixir-ecto/elixir-ecto/ecto (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| elixir-ecto/ectogeneric | >=3.4.0 <3.14.3 | 3.14.3 |
| elixir-ecto/elixir-ecto/ectogeneric | >=cb2f03964dac324a9771f84f5088e395326e6de8 <eef014ad090d27d1a5b69c0e32a50eabd44ab3bb | eef014ad090d27d1a5b69c0e32a50eabd44ab3bb |
Published upstream
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.