CVE-2026-82749: CWE-863 Incorrect Authorization in ash-project ash
Description
Incorrect Authorization vulnerability in ash-project ash widens a relationship's parent(...) scoping filter to match unintended records when the referenced parent field cannot be resolved. Loading a relationship whose filter references parent(...) resolves that expression against the parent record. resolve_parent_in_filter/3 (lib/ash/actions/read/relationships.ex) resolved an unresolvable parent reference (for example when the referenced field was not selected on the source query) to nil rather than failing. A scoping predicate such as org_id == parent(org_id) then becomes an IS NULL match, and a guard like is_nil(parent(org_id)) or org_id == parent(org_id) activates its unrestricted branch, so the relationship returns records the scope was meant to exclude. The fix fails the read with an error when a parent(...) reference cannot be resolved, instead of defaulting to nil. This issue affects ash: from 3.13.2 before 3.32.2.
CVSS v4.0
Score 5.9medium
Affected software
ash-project
ash
ash-project
ash
cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises in ash-project ash when the function resolve_parent_in_filter/3 resolves an unresolvable parent reference to nil instead of failing. This behavior causes scoping predicates that rely on parent(...) references to incorrectly match records where the parent field is missing or not selected, effectively widening the scope and returning unauthorized records. For example, a filter like org_id == parent(org_id) becomes an IS NULL match, activating unrestricted branches in guards such as is_nil(parent(org_id)) or org_id == parent(org_id). The vulnerability affects versions from 3.13.2 before 3.32.2. The remediation is to fail the read operation with an error when the parent(...) reference cannot be resolved, preventing unintended data exposure.
Potential Impact
This vulnerability can lead to unauthorized data access by returning records that should have been excluded by the scoping filter. The incorrect authorization widens the scope of data returned in relationships, potentially exposing sensitive or restricted information. The impact is rated medium with a CVSS score of 5.9, indicating a significant but not critical risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix is to fail the read operation with an error when a parent(...) reference cannot be resolved instead of defaulting to nil. Until an official patch or update is available, users should review their usage of parent(...) references in filters and consider workarounds to avoid unresolved parent references. Monitor vendor communications for an official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-31T01:00:09.774Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a964f9bacd9273b4930b0f4
Added to database: 09/01/2026, 04:07:55 UTC
Last enriched: 09/07/2026, 15:08:10 UTC
Last updated: 10/14/2026, 06:48:21 UTC
Views: 83
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.