Answer in brief
CVE-2026-82586 records a High severity (CVSS 8.2) vulnerability in AshLua read operation aggregate bypasses the exposed-field allow-list, exposing private attributes. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_lua (generic), ash-project/ash_lua (generic), ash-project/ash-project/ash_lua (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.2. 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_lua (generic), ash-project/ash_lua (generic), ash-project/ash-project/ash_lua (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash_luageneric | >=8675e47cca81f36594083a7e63379bac9e123e72 <c0dfcd9494766d548178c37df0bd01cff378e1c7 | c0dfcd9494766d548178c37df0bd01cff378e1c7 |
| ash-project/ash_luageneric | >=0.1.0 <0.2.1 | 0.2.1 |
| ash-project/ash-project/ash_luageneric | >=8675e47cca81f36594083a7e63379bac9e123e72 <c0dfcd9494766d548178c37df0bd01cff378e1c7 | c0dfcd9494766d548178c37df0bd01cff378e1c7 |
Published upstream
Sep 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 7, 2026
Improper Protection of Alternate Path vulnerability in ash-project ash_lua allows a user-supplied Lua script to read attributes that are not on the exposed-field allow-list. AshLua exposes Ash resources to Lua scripts, gated by a manifest declaring which fields are exposed. The read action's operation aggregate path in AshLua.Runtime took the field name straight from the Lua call and resolved it with only String.to_existing_atom and Ash.Query.Aggregate.new!, neither of which consults the exposed-field allow-list the normal fields path enforces. A script can therefore read the value of any attribute of any record the actor may read, including private sensitive?: true columns, via resource.read({ operation = {"list", "hashed_password"} }); min and max give a value oracle. Anyone able to submit or influence a Lua script can reach this. This issue affects ash_lua: from 0.1.0 before 0.2.1.
Quoted source text, attributed separately from HOL analysis.