CVE-2026-82746: CWE-862 Missing Authorization in ash-project ash
Description
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.
CVSS v4.0
Score 5.9medium
Affected software
ash-project
ash
ash-project
ash
cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*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
The vulnerability exists in Ash.Actions.Update.UpdateMany where the atomic update_many operation executes as a single atomic statement without applying resource authorization policies properly. Even when authorization is enabled, the operation updates all rows matched by primary key without enforcing policy filters, allowing unauthorized record updates. The fix involves restricting the atomic path to data layers that support changeset filters, authorizing each changeset individually, and merging policy filters to ensure only authorized rows are updated.
Potential Impact
An attacker with access to the vulnerable function can update records that should be protected by resource policies, such as records belonging to other users or tenants. This can lead to unauthorized data modification and potential data integrity issues. The CVSS 4.0 score is 5.9 (medium severity), reflecting local attack vector with low complexity but partial impact on integrity and requiring partial user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using the atomic update_many path in environments where authorization policies are critical or implement additional access controls outside of Ash.update_many/4 to enforce authorization.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-31T01:00:09.774Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a964c16acd9273b492d1355
Added to database: 09/01/2026, 03:52:54 UTC
Last enriched: 09/07/2026, 14:46:57 UTC
Last updated: 10/15/2026, 06:48:19 UTC
Views: 78
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.