---
id: CVE-2026-77454
title: >-
  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 f…
summary: >-
  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 f…
severity: none
cwe:
  - CWE-863
published: '2026-08-30'
updated: '2026-08-30'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-77454'
references:
  - url: 'https://cna.erlef.org/cves/CVE-2026-77454.html'
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/ash-project/ash_sql/commit/865fdd4e5e70724a23b19c048e6768c31d2209ab
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/ash-project/ash_sql/security/advisories/GHSA-8v9m-8pxv-738c
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: 'https://osv.dev/vulnerability/EEF-CVE-2026-77454'
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
tags:
  - nvd
ingestedAt: '2026-08-30T17:55:39.788Z'
epss: 0.00179
epssPercentile: 0.06592
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
