Vulnerability · CVE-2026-114214
Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records
Published Oct 25, 2026 · catalog updated Oct 25, 2026 · Loading a through relationship
Last checked Oct 26, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-114214. EPSS is 0.25%. Act only if a listed version of Loading a through relationship is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Loading a through relationship).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-48044 · High
- CVE-2025-48043 · High
- CVE-2025-48042 · High
- Severity
- Medium6.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.25%
- Remediation
- Advisory link
- Affected products
- Hex ash · vendor ash-project ash
## Summary Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a relationship. When a relationship declared with was loaded for a single record with a limit of 1, or an unsorted relationship was loaded with a limit of 1, in 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 . The read still runs the destination's policies but carries the relationship as , so a client paging such a field (for example 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. ## Impact A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship. ## Configurations Reachable when a relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource's read policies rely on the relationship ( ) or are otherwise open to the caller.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Hex ash3.24.0 → 3.37.1
- vendor ash-project ashversion unspecified
How to fix CVE-2026-114214
Upgrade
CVE-2026-114214 lists a fix boundary at 3.37.1. Compare the installed build with that boundary before you change production.
Version check
Seen in 3.24.0 → 3.37.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-114214. EPSS is 0.25%. Act only if a listed version of Loading a through relationship is installed.
Which versions are affected?
Compare what you have installed with 3.24.0 → 3.37.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-863: Incorrect Authorization. EPSS 0.25%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 25, 2026 · GitHub Advisory Database
Detected
## Summary Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a relationship. When a relationship declared with was loaded for a single record with a limit of 1, or an unsorted relationship was loaded with a limit of 1, in chose the path that reads the destination without any filter linking it to the source. T
Oct 25, 2026 · GitHub Advisory Database
Fix available
ash fixed in 3.37.1
Oct 25, 2026 · GitHub Advisory Database
Fix available
ash fixed in 3.37.1
Oct 25, 2026 · GitHub Advisory Database
Updated
## Summary Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a relationship. When a relationship declared with was loaded for a single record with a limit of 1, or an unsorted relationship was loaded with a limit of 1, in chose the path that reads the destination without any filter linking it to the source. T
Sources
- CVE.orgVulnerability recordCVE-2026-114214
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
cve.org - FIRST EPSSExploitation probabilityCVE-2026-114214
30-day exploitation probability 0.25%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-g2h4-xp57-q863
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryEEF-CVE-2026-114214
Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records
osv.dev
References
Freshness
Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 26, 2026
- GitHub Advisory DatabaseOct 26, 2026
- OpenSSF OSV / OSV ScannerOct 26, 2026
- CVE.orgOct 26, 2026