CVE-2026-82745
Improper Access Control vulnerability in ash-project ash lets a …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- cna.erlef.org/cves/CVE-2026-82745.html
- github.com/ash-project/ash/commit/912e243196017c2a812c25905c2b1cc3bbb843fc
- github.com/ash-project/ash/security/advisories/GHSA-92x7-q3h5-wf88
- osv.dev/vulnerability/EEF-CVE-2026-82745
- github.com/ash-project/ash/commit/6dc699d8a683d542812b34a8c104cc90164add3a
- nvd.nist.gov/vuln/detail/CVE-2026-82745
- cve.org/CVERecord?id=CVE-2026-82745
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.