ZeroHour

CVE-2026-82586

niche

Attribute allow-list bypass in ash_lua exposes sensitive fields to Lua scripts

CVSS 4.0
8.2 high
EPSS
<1%p26
Published
()
Modified
AI analysis

CVE-2026-82586 is an improper-protection-of-alternate-path flaw (CWE-424) in the ash_lua package for the Ash Framework, affecting versions from 0.1.0 before 0.2.1, with a CVSS 4.0 base score of 8.2 (High). AshLua exposes Ash resources to Lua scripts through a manifest declaring which fields are exposed, but the read action's operation aggregate path in AshLua.Runtime takes the field name straight from the Lua call and resolves it with only String.to_existing_atom and Ash.Query.Aggregate.new!, never consulting the exposed-field allow-list that the normal fields path enforces. An attacker who can submit or influence a Lua script can therefore read the value of any attribute of any record the actor is permitted to read, including private columns marked sensitive, with aggregate operations such as min or max serving as a value oracle. This yields disclosure of confidential data (for example password hashes) but no integrity or availability impact, and exploitation requires access to an AshLua-enabled application where the attacker can control script content. No public proof-of-concept or in-the-wild exploitation is known; the flaw is not in CISA KEV and EPSS estimates roughly a 0.3% probability of exploitation within 30 days.

What to do: Upgrade ash_lua to 0.2.1 or later. Until patched, audit and restrict submitted Lua scripts so field names are not passed into aggregate operations (or disable AshLua-backed read paths), and review whether sensitive attributes such as hashed_password could have been read by scripts already executed.

Affected
ash-project ash_lua>= 0.1.0 and < 0.2.1
Estimated exposure
nichelikely hundreds to low thousands of application deployments — ash_lua is a specialized pre-1.0 extension within the Ash Framework Elixir ecosystem with no published install counts, and the flaw only matters where an application exposes resources to user-submitted or user-influenced Lua scripts, so…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

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.

Weakness
CWE-424
Vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In the news

No ingested article mentions this CVE yet.