cve.bz

CVE-2026-82586 AshLua read operation aggregate bypasses the exposed-field allow-list, exposing private attributes

8.2 highEPSS 0.5%Fix available

High (8.2) in ash-project ash lua. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in ash_lua 0.2.1.

On this page
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.

Severity

CVSS 4.0

8.2 high
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
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-424 Improper Protection of Alternate Path
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash_lua (Hex): fixed in 0.2.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-82586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-82586?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-82586?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-82586 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ash-project ash_luafrom 0.1.0 before 0.2.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-82586Hexash_lua>=0.1.0 <0.2.10.2.1
EEF-CVE-2026-82586v0.2.0, v0.1.6, v0.1.5, v0.1.4, v0.1.3 and 3 moreno fix published

Attack patterns (CAPEC)

  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium
  • CAPEC-554 Functionality Bypass Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON