Is CVE-2026-114214 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114214 being exploited in the wild.

How severe is CVE-2026-114214?

Informational severity, published 25 October 2026.

Which products and versions are affected?

Ash-Project Ash 3.24.0 to 3.37.0.

Is there a fix for CVE-2026-114214?

Yes: fixed in 3.37.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114214 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-114214?

Check whether you run Ash-Project Ash at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114214: ash-project ash incorrect authorization in relationships

CVE-2026-114214 · Severity: info · Published 2026-10-25

Ash is a data framework for building Elixir applications. A flaw in how the framework loads related records allows an authenticated client to enumerate and read records they shouldn't have access to by paging through relationships. An attacker can systematically retrieve sensitive data from the destination resource that would normally be protected by access policies.

Technologies: Ash-Project Ash. Vendors: Ash-Project.

Quick answers

Is CVE-2026-114214 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114214 being exploited in the wild.
How severe is CVE-2026-114214?: Informational severity, published 25 October 2026.
Which products and versions are affected?: Ash-Project Ash 3.24.0 to 3.37.0.
Is there a fix for CVE-2026-114214?: Yes: fixed in 3.37.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114214 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-114214?: Check whether you run Ash-Project Ash at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.37.1

Technical details

An incorrect authorization vulnerability in ash's lateral_join?/4 function (lib/ash/actions/read/relationships.ex) fails to apply source-to-destination filters when loading has_many through relationships with limit: 1 or unsorted has_one through relationships with limit: 1. The destination policies still run with the relationship context (accessing_from), but because the join filter is omitted, an attacker can page through records using offset/limit to enumerate all records the policy permits in that context.

Affected products

ash-project ash 3.24.0 to 3.37.0

Timeline

2026-10-25: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.