Ash.update_many/4 atomic path skips resource policy authorization, allowing updates to forbidden records
## Summary Missing Authorization vulnerability in ash-project ash allows an actor to update records forbidden by resource policies through the atomic path of `Ash.update_many/4`. `Ash.update_many/4` runs as a single atomic statement (a data-layer `update_many`, for example a SQL MERGE) whenever an atomic strategy is used and the data layer supports it. `Ash.Actions.Update.UpdateMany` (`lib/ash/actions/update/update_many.ex`) took that path even under `authorize?: true` without applying the resource's policies, so the statement updated every row matched by primary key regardless of the policy filter that authorization would impose. An actor could therefore update records the policies forbid, such as rows belonging to another actor or tenant. The fix restricts the atomic path to data layers supporting changeset filters when authorizing, authorizes each changeset, and merges the resulting policy filter into each changeset so the statement only touches authorized rows. This issue affects ash: from 3.29.0 before 3.32.2.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-82746US | —OT elevated | — | ||
Missing Authorization vulnerability in ash-project ash allows an actor to update records forbidden by resource policies through the atomic path of Ash.update_many/4.
Ash.update_ma… | ||||
references
External citations — patches, advisories, analysis.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan