Vulnerability EEF-CVE-2026-82745

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
2 months ago
September 01, 2026 at 03:42 AM UTC
ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness
0.4.0 - 3.32.1
0.4.0 - 3.32.1

Summary

ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness

Details

Summary

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.

Impacted packages

Timeline

Published
2 months ago
September 01, 2026 at 03:42 AM UTC
Fixed (3.32.2)
2 months ago
September 01, 2026 at 03:02 AM UTC
Last Modified
20 hours ago
November 21, 2026 at 05:23 PM UTC