{"id":"CVE-2026-78216","aliases":["EEF-CVE-2026-78216","EUVD-2026-72931","GHSA-5whv-8rcp-x33j"],"status":"published","title":"AshLua eval read operations can read field-policy-protected fields via aggregates","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.\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.","severity":{"version":"4.0","score":6,"vector":"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","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00427,"percentile":0.37433,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1220"],"published":"2026-09-08T16:42:20Z","modified":"2026-10-28T02:30:44Z","fixes":[{"ecosystem":"Hex","package":"ash_lua","fixed_in":["0.2.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Hex","package":"ash_lua","ranges":[{"type":"SEMVER","events":[{"introduced":"0.1.0"},{"fixed":"0.2.2"}]}],"versions":["0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.2.0","0.2.1"]}],"products":[{"vendor":"ash-project","product":"ash_lua"}],"references":[{"url":"https://github.com/ash-project/ash_lua/security/advisories/GHSA-5whv-8rcp-x33j","tags":["vendor-advisory","advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-78216.html","tags":["related","web"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-78216","tags":["related","web"]},{"url":"https://github.com/ash-project/ash_lua/commit/8675e47cca81f36594083a7e63379bac9e123e72","tags":["related","fix","web"]},{"url":"https://github.com/ash-project/ash_lua/commit/266a5dcc56d5015b6d316c10606169e753b07450","tags":["patch","fix"]},{"url":"https://github.com","tags":["web"]},{"url":"https://repo.hex.pm","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/78xxx/CVE-2026-78216.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-78216","tags":["advisory"]},{"url":"https://github.com/ash-project/ash_lua","tags":["package"]},{"url":"https://hex.pm/packages/ash_lua","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-78216","title":"AshLua eval read operations can read field-policy-protected fields via aggregates","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.\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.","status":"published","published":"2026-09-08T16:42:20.908Z","modified":"2026-09-08T17:27:08.856Z","cvss":[{"version":"4.0","score":6,"vector":"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","level":"medium","assessor":"cna"}],"cwes":["CWE-1220"],"updated_at":"2026-11-02T13:34:48.658051Z"}],"euvd":[{"id":"EUVD-2026-72931","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.\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.","status":"published","published":"2026-09-08T16:42:20Z","modified":"2026-09-08T17:27:08Z","cvss":[{"version":"4.0","score":6,"vector":"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","level":"medium"}],"updated_at":"2026-11-02T17:28:28.997972Z"}],"nvd":[{"id":"CVE-2026-78216","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.\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.","status":"published","published":"2026-09-08T17:18:30.653Z","modified":"2026-09-08T19:29:09.68Z","cvss":[{"version":"4.0","score":6,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"}],"cwes":["CWE-1220"],"updated_at":"2026-11-02T14:12:44.436435Z"}],"osv":[{"id":"CVE-2026-78216","title":"AshLua eval read operations can read field-policy-protected fields via aggregates","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.\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.","status":"published","published":"2026-09-08T16:42:20.908Z","modified":"2026-10-28T02:30:44.903380896Z","cvss":[{"version":"4.0","score":6,"vector":"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","level":"medium"}],"cwes":["CWE-1220"],"updated_at":"2026-11-02T15:45:17.44708Z"},{"id":"EEF-CVE-2026-78216","title":"AshLua eval read operations can read field-policy-protected fields via aggregates","description":"## Summary\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## Configurations\n\nReachable only when an application exposes an AshLua `eval` action over a resource whose field policies restrict a field that the calling actor can still name as an operation aggregate (for example a `public? true` but field-policy-protected attribute).","status":"published","published":"2026-09-08T16:42:20.908Z","modified":"2026-09-08T16:56:02.903287963Z","cvss":[{"version":"4.0","score":6,"vector":"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","level":"medium"}],"cwes":["CWE-1220"],"updated_at":"2026-11-02T15:46:33.520522Z"}]}}