Vulnerability · Published Sep 1, 2026 · Assigned by EEF
CVE-2026-82745ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness
Medium 5.9
In plain English
A medium-severity improper access control in ash from ash-project. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities).
Official description
Improper Access Control vulnerability in ash-project ash lets a create action overwrite an existing record when the ETS or Mnesia data layer is used, because neither enforced primary-key uniqueness on insert. Unlike a SQL data layer, whose unique primary-key constraint rejects a duplicate, the ETS and Mnesia data layers implemented create as a keyed insert that replaces any existing entry with the same primary key (lib/ash/data_layer/ets/ets.ex, lib/ash/data_layer/mnesia/mnesia.ex). An actor who can set the primary key on a create (for example a user-supplied string or integer key) can submit a create whose key matches an existing record and silently overwrite it, destroying and replacing another entity's data without going through the update action or its policies. The fix rejects a create whose primary key already exists with an already-taken error, and only allows duplicates for keyless resources. This issue affects ash: from 0.4.0 before 3.32.2.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| ash-project | ash | 0.4.0 – before 3.32.2 |
| ash-project | ash | 6dc699d8a683d542812b34a8c104cc90164add3a – before 912e243196017c2a812c25905c2b1cc3bbb843fc |
Weakness: CWE-284 · Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N