Ash.update_many/4 was designed to perform a single atomic update using a data‑layer operation such as SQL MERGE. The vulnerability stems from the fact that, when the optional authorize?: true flag is used, the atomic path still bypasses the resource policy checks. Consequently, an attacker can issue a single update_many call that changes rows belonging to other users, tenants, or otherwise protected data. The flaw is a privilege escalation flaw classified as CWE‑862 and can lead to unauthorized data integrity violations.

The affected product is the open‑source Ash web framework by the ash‑project. Versions from 3.29.0 up to, but not including, 3.32.2 are affected. Any deployment without an upgrade to 3.32.2 or newer must be considered vulnerable.

The CVSS v3 score is 5.9, indicating a moderate severity for accidental or targeted exploitation. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a legitimate API consumer of the framework that opts into authorization checks while invoking the bulk update helper. Since the atomic path bypasses policy enforcement, a malicious actor with any valid user session could craft a payload that updates records owned by another tenant, thus compromising multiple aspects of confidentiality and integrity. No additional exploitation steps are required beyond executing the update_many call.