cve.bz

CVE-2026-114214 ash-project ash: Incorrect Authorization

6.0 mediumEPSS 0.2%Fix available

Medium (6.0) in ash-project ash. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in ash 3.37.1.

On this page
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.

Severity

CVSS 4.0

6.0 medium
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
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash (Hex): fixed in 3.37.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-114214 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114214?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114214?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114214 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ash-project ashfrom 3.24.0 before 3.37.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-114214Hexash>=3.24.0 <3.37.13.37.1
EEF-CVE-2026-114214v3.37.0, v3.36.1, v3.36.0, v3.35.0, v3.34.6 and 50 moreno fix published

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having Moderate impact for Red Hat because exploitation requires authenticated API access to specific through-relationship queries and results in information disclosure without affecting system integrity or availability. The Ash framework is not included or supported in Red Hat Enterprise Linux or other Red Hat enterprise products. Consequently, default enterprise deployments are not exposed to this flaw, which is restricted to custom applications built directly on the affected library.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-114214.

References

Check your stackJSON