---
id: "CVE-2026-114214"
kind: "vulnerability"
aliases: ["CVE-2026-114214"]
title: "Ash: through-relationship loads leak unrelated destination records to clients"
severity: "medium"
cvss: 6.0
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["ash", "ashgraphql", "elixir", "package", "self-hosted"]
not_affected_if: ["ash-below-3.24.0-or-above-3.37.1", "no-client-paging", "no-through-relationships"]
published_at: "2026-10-25T20:16:31+00:00"
first_seen_at: "2026-10-25T20:35:47+00:00"
updated_at: "2026-10-25T20:37:44+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114214", "first_seen_at": "2026-10-25T20:35:47+00:00"}]
---

# Ash: through-relationship loads leak unrelated destination records to clients

Ash's has_many :through and has_one :through loads with a limit of 1 can return destination records not linked to the source record. A client paging such a field, for example through AshGraphql, can enumerate records that policies allow only via that relationship.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Ash version in `mix.lock` or `mix deps | grep ash`
- Search the code for `has_many` or `has_one` declarations using `through:` and for paginated access to them with limit and offset

## Fix

- Upgrade `ash` to `3.37.1` or later
- Until upgraded, avoid exposing `through:` relationships with limit and offset to clients

## Timeline

- 2026-10-25T20:35:47+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-114214

## From the sources

Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a through relationship.

When a has_many relationship declared with through: was loaded for a single record with a limit of 1, or an unsorted has_one through relationship was loaded with a limit of 1, lateral_join?/4 in lib/ash/actions/read/relationships.ex chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an offset. The read still runs the destination's policies but carries the relationship as accessing_from, so a client paging such a field (for example teachers(limit: 1, offset: n) through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.

This issue affects ash: from 3.24.0 before 3.37.1.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_