Answer in brief
CVE-2026-82564 records a High severity (CVSS 7.1) vulnerability in Identity tool filter in AshAi accepts operator maps, allowing update or destroy of unidentified records. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_ai (generic), ash-project/ash_ai (generic), ash-project/ash-project/ash_ai (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 7.1. 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_ai (generic), ash-project/ash_ai (generic), ash-project/ash-project/ash_ai (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash_aigeneric | >=bc2122f78fca6c11d8ec2b9ac53148ec17476460 <87f616d5bfbf7af43346f0701ae17f853789a602 | 87f616d5bfbf7af43346f0701ae17f853789a602 |
| ash-project/ash_aigeneric | >=0.6.0 <1.0.0 | 1.0.0 |
| ash-project/ash-project/ash_aigeneric | >=bc2122f78fca6c11d8ec2b9ac53148ec17476460 <87f616d5bfbf7af43346f0701ae17f853789a602 | 87f616d5bfbf7af43346f0701ae17f853789a602 |
Published upstream
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 31, 2026
Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash_ai allows a caller of an identity-configured tool to update or destroy records it never identified, including every row in the table. In AshAi.Tool.Execution, identity_filter/3 built the update/destroy filter directly from the raw tool arguments as [{key, Map.get(arguments, to_string(key))}] and passed it to Ash.Query.do_filter/2. A map value is parsed as a predicate expression rather than a literal, so a caller can send {"public_ref": {"not_eq": "<own-ref>"}} and, combined with Ash.Query.limit(1) and Ash.bulk_update!/Ash.bulk_destroy!, retarget the write at a record it never identified; an omitted key yields an IS NULL filter that matches an arbitrary row. The fix casts each identity value to the field type, rejecting non-scalar inputs. This issue affects ash_ai: from 0.6.0 before 1.0.0.
Quoted source text, attributed separately from HOL analysis.