CVE-2026-82586: AshLua read operation aggregate bypasses the exposed-field allow-list, exposing private attributes
Improper Protection of Alternate Path vulnerability in ash-project ashlua 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.toexistingatom 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", "hashedpassword"} }); min and max give a value oracle. Anyone able to submit or influence a Lua script can reach this.
This issue affects ashlua: from 0.1.0 before 0.2.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ash-project ash_luato a version that resolves this vulnerability.Fixed in 0.2.1
Event History
Frequently Asked Questions
Who can exploit this issue?
Anyone able to submit or influence a Lua script processed by AshLua can exploit it. The script can target attributes on records that the acting actor is already permitted to read.
Are private or sensitive attributes exposed?
Yes. The aggregate read path does not consult the manifest's exposed-field allow-list, so it can read attributes outside that list, including private columns marked sensitive?: true.
What access does an attacker need to retrieve a value?
The attacker needs to invoke the read operation aggregate path with a field name, such as a list aggregate. Min and max aggregates can also be used as a value oracle.
Which versions are affected?
ash_lua versions from 0.1.0 up to, but not including, 0.2.1 are affected.