Vulnerability · Published Nov 4, 2026 · Assigned by EEF

CVE-2026-118391Unbounded query cache growth from interpolated JSON paths and splice lists in Ecto

High 8.9

In plain English

A high-severity resource allocation without limits in ecto from elixir-ecto. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 43% of all known vulnerabilities).

Severity (CVSS 4.0)8.9High
Exploit odds (30 days)0.5%top 57.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected products (as reported)

VendorProductVersions
elixir-ecto ecto 3.4.0 – before 3.14.3
elixir-ecto ecto cb2f03964dac324a9771f84f5088e395326e6de8 – before eef014ad090d27d1a5b69c0e32a50eabd44ab3bb

Weakness: CWE-770 · Vector: 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

References