Skip to content
Connect AISign inSign up free
CVE-2026-782166.0MediumCWE-1220

CVE-2026-78216: AshLua eval read operations can read field-policy-protected fields via aggregates

ash-project · ash_lua

Fixed in 0.2.2 · Affected: ash-project ash_lua before 0.2.2 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
37th percentile
050100

Higher than 37% of scored CVEs

6.0MediumCVSS 4.0
LowMedium

DescriptionCVE.org

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.

Affected products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ash-project · ash_luafrom 0.1.0 before 0.2.2
  • ash-project · ash_luaVersions not stated

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template

CoverageNo articles yet

No CyberSIXT article names CVE-2026-78216 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References