Read the docs
TI-2026-80104 Aliases CVE-2026-114214

Incorrect authorization in Ash through relationship loading

Priority LOW 26CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.

Summary

The ash-project ash package from 3.24.0 before 3.37.1 loads a through relationship with a limit of 1 without filtering destination records by the source record (CWE-863). A remote client with low privileges can page through such a field to read destination records unrelated to the source.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00246 15th percentileScored 2026-11-07
Fix Fixed ash (ash-project): 3.37.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ash-projectash3.24.0 to before 3.37.13.37.1Patch availableCNA
  • ash Vendorash-project Affected 3.24.0 to before 3.37.1 Fixed in 3.37.1 Patch available CNA

CPE names CNA · 1

CPEVersionsRoleVendor
cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*———
  • cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:* Versions — — ·—

Remediation

Update ash-project ash to version 3.37.1 or later, which fixes this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA ash (ash-project) Fixed in 3.37.1

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-25 Threatist record created from CVE-2026-114214
  2. 2026-10-25 Affected versions changed · Red Hat
  3. 2026-10-25 CVSS score added · Red Hat
  4. 2026-10-26 CISA SSVC decision points changed
  5. 2026-10-26 Priority changed: MEDIUM → LOW

References

  • TI-2026-56298 Query-complexity limit bypass via first/last pagination arguments in AshGraphql enables denial of service CVSS 4.0HIGH 8.7
  • TI-2026-52572 Unbounded atom creation from client-supplied RPC field names in AshTypescript field formatter CVSS 4.0HIGH 8.7
  • TI-2026-57010 Path traversal in AshAdmin file uploads via unsanitized client filename CVSS 4.0HIGH 8.3
  • TI-2026-26840 Ash Framework: Ash.Type.Module.cast_input/2 atom exhaustion via unchecked Module.concat allows BEAM VM crash CVSS 4.0HIGH 8.2
  • TI-2026-54252 EEx template evaluation of prompt content in AshAi enables remote code execution CVSS 4.0HIGH 8.9
  • TI-2026-54208 Stored XSS in AshAdmin relationship typeahead via unescaped label_field content CVSS 4.0HIGH 8.4
See all 90 →

Sources