exists/2 predicate silently dropped on limited relationships with a parent() filter in AshSql (CVE-2026-77454) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-77454

exists/2 predicate silently dropped on limited relationships with a parent() filter in AshSql

Answer in brief

CVE-2026-77454 records a Unknown severity vulnerability in exists/2 predicate silently dropped on limited relationships with a parent() filter in AshSql. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 30, 2026Updated Aug 30, 2026Source checked Aug 30, 2026First seen by HOL Aug 30, 2026Material review Aug 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ash_sqlgeneric	>=0.4.1 <0.7.1	0.7.1
ash-project/ash_sqlgeneric	>=e26a63b29bd7501505fafd726f14262cdc3b6629 <865fdd4e5e70724a23b19c048e6768c31d2209ab	865fdd4e5e70724a23b19c048e6768c31d2209ab

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash_sql, ash-project/ash_sql.
Review the reported fix. Update ash-project/ash_sql to 0.7.1; ash-project/ash_sql to 865fdd4e5e70724a23b19c048e6768c31d2209ab if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 30, 2026

Sources and claim methodology

Upstream source description

Incorrect Authorization vulnerability in ash-project ash_sql allows a caller to bypass a scoping or authorization filter expressed as exists/2 over a relationship that declares both a limit (or from_many?) and a parent(...)-referencing filter or sort. AshSql.Join.related_query/3 skips the caller-supplied exists predicate for such relationships and delegates it to limit_from_many/5. When the relationship's own filter or sort references parent(...), limit_from_many/5 takes a branch that drops both the limit and the predicate, emitting a bare correlated EXISTS with no predicate. The check then matches any record that has any related row. Most severely, when the expression backs a policy (for example authorize_if expr(exists(memberships, user_id == ^actor(:id)))), the actor-scoping condition disappears and the policy passes for any actor with any related row. This issue affects ash_sql: from 0.4.1 before 0.7.1.

Quoted source text, attributed separately from HOL analysis.