{"id":"CVE-2026-78216","title":"AshLua exposes Ash read actions to Lua scripts run through an eval action","summary":"AshLua exposes Ash read actions to Lua scripts run through an eval action. A read call accepts an operation (list, min, max, first, sum, avg) that builds an ad-hoc Ash.Query.Aggregate over a named field and returns its raw value.\n\nAsh fi…","severity":"medium","cvss":6,"cvssVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","cwe":["CWE-1220"],"vendor":"ash-project","product":"ash_lua","affected":["ash_lua >= 0.1.0 < 0.2.2","ash-project/ash_lua >= 8675e47cca81f36594083a7e63379bac9e123e72 < 266a5dcc56d5015b6d316c10606169e753b07450"],"published":"2026-09-08","updated":"2026-09-08","sourceUpdated":"2026-09-08T19:29:09.680","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-78216","references":[{"url":"https://cna.erlef.org/cves/CVE-2026-78216.html","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://github.com/ash-project/ash_lua/commit/266a5dcc56d5015b6d316c10606169e753b07450","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://github.com/ash-project/ash_lua/commit/8675e47cca81f36594083a7e63379bac9e123e72","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://github.com/ash-project/ash_lua/security/advisories/GHSA-5whv-8rcp-x33j","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-78216","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}],"tags":["nvd","cve.org"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-08T17:26:34.675766Z"},"cvssSource":"cna","ingestedAt":"2026-09-08T19:08:49.600Z","epss":0.00246,"epssPercentile":0.16148,"slug":"CVE-2026-78216","body":"## Overview\n\nAshLua exposes Ash read actions to Lua scripts run through an eval action. A read call accepts an operation (list, min, max, first, sum, avg) that builds an ad-hoc Ash.Query.Aggregate over a named field and returns its raw value.\n\nAsh field policies redact forbidden fields on returned records (replacing them with %Ash.ForbiddenField{}), but that redaction does not apply to aggregate values. A script could therefore read a field the calling actor's field policies forbid by requesting it as an aggregate instead of as a field. This includes fields that are public? true but restricted per-actor by a field policy, such as sensitive PII. The prior hardening only enforced the exposed-field allow-list (field visibility), which is a separate axis from per-actor field-policy authorization.\n\nThe fix authorizes the aggregated field against the resource's field policies, so aggregating over a field the actor may not see is refused or scoped to the rows where it is visible.\n\nThis issue affects ash_lua: from 0.1.0 before 0.2.2.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":33,"depthScoreParts":{"impact":33,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}