cve.bz

CVE-2026-96581 ash-project ash

7.6 highEPSS 0.3%Fix available

High (7.6) in ash-project ash. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in ash 3.37.2.

On this page
Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take over another tenant's records via an upserting create action. Under attribute multitenancy, Ash.Actions.Create (lib/ash/actions/create/create.ex) and Ash.Actions.Create.Bulk (lib/ash/actions/create/bulk.ex) upserted on the primary key, or on an all_tenants? identity, without scoping the conflicting record to the request's tenant. A caller of a create action with upsert? true that accepts the primary key, supplying a record id from another tenant, updated that record's upsert fields and received all of its attributes in the result. With the default upsert fields the tenant attribute was written too, moving the record into the caller's tenant. Read and update policies do not run for upserts, and tenant-scoped create policies pass because the tenant is the caller's own. This issue affects ash: from 1.22.0 before 3.37.2.

Severity

CVSS 4.0

7.6 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash (Hex): fixed in 3.37.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-96581 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96581?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96581?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96581 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ash-project ashfrom 1.22.0 before 3.37.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-96581Hexash>=1.22.0 <3.37.23.37.2
EEF-CVE-2026-96581v3.37.1, v3.37.0, v3.36.1, v3.36.0, v3.35.0 and 802 moreno fix published

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an authenticated tenant can cross isolation boundaries to read, alter, or claim ownership of records belonging to other tenants, compromising both confidentiality and data integrity. The issue only manifests in multitenant application deployments utilizing upsert actions on primary keys or global identities. Red Hat Enterprise Linux and other supported Red Hat software do not package or deploy the Ash framework, so default Red Hat environments are not exposed to this risk.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-96581.

References

Check your stackJSON