Answer in brief
CVE-2026-82742 records a Medium severity (CVSS 5.9) vulnerability in Ash.Filter.Runtime materializes a combinatorial cross-product over to-many relationships, exhausting memory. The current sources do not mark it as known exploited. The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (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 5.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 ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ashgeneric | >=f6f5d194bfc7802bd32e48bf2eabd2d97a0109a4 <da07f009e889819ec410fa1f0f12534bfb9e21dd | da07f009e889819ec410fa1f0f12534bfb9e21dd |
| ash-project/ashgeneric | >=1.29.0-rc0 <3.32.2 | 3.32.2 |
| ash-project/ash-project/ashgeneric | >=f6f5d194bfc7802bd32e48bf2eabd2d97a0109a4 <da07f009e889819ec410fa1f0f12534bfb9e21dd | da07f009e889819ec410fa1f0f12534bfb9e21dd |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
Uncontrolled Resource Consumption vulnerability in ash-project ash lets an attacker exhaust node memory by matching a filter that spans multiple to-many relationships in memory. Ash.Filter.Runtime matches a filter against an in-memory record by first expanding the record into combinations of its related rows. flatten_relationships/2 (lib/ash/filter/runtime.ex) eagerly built the full Cartesian product across the filter's to-many relationship paths, so a record with K to-many relationships of M rows each materialized on the order of M^K scenarios before any predicate was checked. A filter or dataset that reaches several sizeable to-many relationships therefore allocates memory combinatorially and can exhaust the node. The fix streams the expansion lazily and short-circuits on the first matching scenario, bounding the work. This issue affects ash: from 1.29.0-rc0 before 3.32.2.
Quoted source text, attributed separately from HOL analysis.