ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-118391

Unbounded query cache growth from interpolated JSON paths and splice lists in Ecto

Published Nov 4, 2026 · catalog updated Nov 4, 2026 · Unbounded query cache growth

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-118391. EPSS is 0.49%. Act only if a listed version of Unbounded query cache growth is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Unbounded query cache growth).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.49%
Remediation
Advisory link
Affected products
Hex ecto · vendor elixir-ecto ecto

## Summary 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 , or . 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 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. ## Details **1. Cache keys** ( , ) checks interpolated path elements with , and a whole interpolated path with , at runtime and places the resulting strings and integers in the expression instead of in the query parameters. builds the cache key from the query expressions, so every distinct path is a distinct key. keeps the values as parameters but expands into one placeholder per element. marks parameters as not cacheable but keeps parameters cacheable, so every distinct list length is a distinct key, and the entry grows with the length. **2. Cache storage** ( , ) stores each new query with in the table that creates with , and nothing removes entries. ecto_sql renders the path into the SQL text, for example , and Postgrex prepares a named statement for each new SQL text on the connection that runs it. **3. Effect** Each request with a new key or list length adds memory that is never released, in the BEAM, where the cache is shared by the whole repository, and with ecto_sql in the database server, where prepared statements are kept per connection. Large keys amplify this: every 1 MB of request data retained about 2 MB in the application and 3 MB in Postgr

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Hex ecto3.4.0 → 3.14.3
  • vendor elixir-ecto ectoversion unspecified

How to fix CVE-2026-118391

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-118391. EPSS is 0.49%. Act only if a listed version of Unbounded query cache growth is installed.

Which versions are affected?

Compare what you have installed with 3.4.0 → 3.14.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.49%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 4, 2026 · GitHub Advisory Database

    Detected

    ## Summary 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 , or . Ecto caches prepared queries per repository in an ETS table with no size limit and n

  2. Nov 4, 2026 · GitHub Advisory Database

    Fix available

    ecto fixed in 3.14.3

  3. Nov 4, 2026 · GitHub Advisory Database

    Fix available

    ecto fixed in 3.14.3

  4. Nov 4, 2026 · GitHub Advisory Database

    Updated

    ## Summary 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 , or . Ecto caches prepared queries per repository in an ETS table with no size limit and n

Sources

  • CVE.orgVulnerability recordCVE-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 inter

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-118391

    30-day exploitation probability 0.49%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-cxjx-vmm2-qr8r

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryEEF-CVE-2026-118391

    Unbounded query cache growth from interpolated JSON paths and splice lists in Ecto

    osv.dev

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 5, 2026
  • GitHub Advisory DatabaseNov 5, 2026
  • OpenSSF OSV / OSV ScannerNov 5, 2026
  • CVE.orgNov 4, 2026