Quick answers
- Is CVE-2026-96581 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96581 being exploited in the wild.
- How severe is CVE-2026-96581?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Ash-Project Ash 1.22.0 before 3.37.2.
- Is there a fix for CVE-2026-96581?
- Yes: fixed in 3.37.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96581 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96581?
- Check whether you run Ash-Project Ash at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.37.2
Technical details
The vulnerability exists in Ash.Actions.Create and Ash.Actions.Create.Bulk when upsert? is true and the action accepts a primary key. When an upsert is performed on records identified by primary key or an all_tenants? identity, the conflicting record is not scoped to the requesting tenant. An attacker can supply a primary key from another tenant and update that record's fields, including the tenant attribute itself, moving the record to their tenant. Read and update policies are bypassed during upserts, and tenant-scoped create policies pass because the attacker provides their own tenant value.
Affected products
- ash-project ash 1.22.0 before 3.37.2
Timeline
- 2026-10-26: disclosed