CVE-2026-78216: CWE-1220 Insufficient Granularity of Access Control in ash-project ash_lua
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. Ash 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. The 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. This issue affects ash_lua: from 0.1.0 before 0.2.2.
AI Analysis
Technical Summary
AshLua allows Lua scripts to perform read actions that include aggregate operations (list, min, max, first, sum, avg) over named fields. While Ash field policies redact forbidden fields on returned records, this redaction does not apply to aggregate values. Consequently, a script can access fields restricted by per-actor field policies by requesting aggregates instead of direct field reads. This includes fields marked public? true but restricted by actor-specific policies, such as sensitive personally identifiable information (PII). The vulnerability affects ash_lua versions from 0.1.0 before 0.2.2. The patch authorizes aggregated fields against resource field policies, refusing or scoping aggregates to visible rows only.
Potential Impact
An actor with limited read permissions can bypass per-actor field policy restrictions by requesting aggregate values of forbidden fields, potentially exposing sensitive data such as PII that should be redacted. This undermines the intended access control granularity and could lead to unauthorized data disclosure.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix enforces authorization of aggregated fields against field policies, preventing unauthorized aggregate reads. Users should upgrade to ash_lua version 0.2.2 or later once available. Until then, restrict Lua script eval actions or limit actor permissions to minimize exposure.
CVE-2026-78216: CWE-1220 Insufficient Granularity of Access Control in ash-project ash_lua
Description
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. Ash 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. The 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. This issue affects ash_lua: from 0.1.0 before 0.2.2.
CVSS v4.0
Score 6.0medium
Affected software
cpe:2.3:a:ash-project:ash_lua:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
AshLua allows Lua scripts to perform read actions that include aggregate operations (list, min, max, first, sum, avg) over named fields. While Ash field policies redact forbidden fields on returned records, this redaction does not apply to aggregate values. Consequently, a script can access fields restricted by per-actor field policies by requesting aggregates instead of direct field reads. This includes fields marked public? true but restricted by actor-specific policies, such as sensitive personally identifiable information (PII). The vulnerability affects ash_lua versions from 0.1.0 before 0.2.2. The patch authorizes aggregated fields against resource field policies, refusing or scoping aggregates to visible rows only.
Potential Impact
An actor with limited read permissions can bypass per-actor field policy restrictions by requesting aggregate values of forbidden fields, potentially exposing sensitive data such as PII that should be redacted. This undermines the intended access control granularity and could lead to unauthorized data disclosure.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix enforces authorization of aggregated fields against field policies, preventing unauthorized aggregate reads. Users should upgrade to ash_lua version 0.2.2 or later once available. Until then, restrict Lua script eval actions or limit actor permissions to minimize exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-31T00:45:02.446Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa03d69acd9273b49f0b3f8
Added to database: 09/08/2026, 16:52:57 UTC
Last enriched: 09/08/2026, 17:08:28 UTC
Last updated: 09/09/2026, 00:43:04 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.