Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-82586Published 2026-09-07

CVE-2026-82586 — ash-project ash_lua

high (derived)

As of 2026-09-08, CVE-2026-82586 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in ash-project ash_lua, CVSS v4.0 8.2, EPSS 0.3% (25.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-82586 as of 2026-09-08; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
8.2/10High (derived)
EPSS
0.3%Higher than 25.6% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
5.1/10Threadlinqs triage score
Published
Updated 2026-09-08
CVSS v4.0 8.2 (High, derived from score) · EPSS 0.3% (higher than 25.6% of all scored CVEs) · Priority 5.1/10 · Published 2026-09-07

Last updated:

What is CVE-2026-82586?

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.

The record classifies CVE-2026-82586 under weakness class CWE-424. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 73 days ago.

Severity and exploitation probability

CVSS v4.0 base score
8.2 — High (derived from score)
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 (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 25.6% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-07

Is CVE-2026-82586 being exploited?

It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-82586

Patch reference: https://github.com/ash-project/ash_lua/commit/c0dfcd9494766d548178c37df0bd01cff378e1c7. Vendor advisory: https://github.com/ash-project/ash_lua/security/advisories/GHSA-37jv-wc37-fhcw. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-82586

No threat campaign in the Threadlinqs corpus currently references CVE-2026-82586, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references