Threat Intelligence Database

CVE-2026-78693 is a vulnerability in ash-project's ash_graphql component that causes error messages to expose internal field names despite application-level redaction configurations. This occurs because the error handling mechanism reinjects internal attribute and argument names into error paths when no field name mapping is configured, leading to leakage of sensitive internal information. The issue affects versions from 1.9.0 up to but not including 1.11.0. The vulnerability has a medium severity score of 6.9 and does not currently have an official patch or remediation guidance.

CVE-2026-80223 is an incorrect authorization vulnerability in ash-project's ash_graphql component. It allows an authenticated subscriber in one tenant to receive records belonging to another tenant via GraphQL subscriptions. The flaw arises because tenant scoping is applied during query building and data-layer prefixing, but not during in-memory policy evaluation of subscription notifications. This leads to cross-tenant data leakage when subscription notifications are authorized in memory without tenant checks. The issue affects versions from 1.4.0 up to but not including 1.11.0.

CVE-2026-81636 is a high-severity vulnerability in ash-project's ash_graphql component that allows unauthenticated clients to bypass GraphQL query complexity limits. This flaw arises because the query complexity calculation does not properly account for Relay connection pagination parameters (first and last), enabling unbounded database reads. The issue affects versions from 0.16.23 up to but not including 1.11.0. No official patch or remediation guidance is currently confirmed.

CVE-2026-81633 is an improper input validation vulnerability in ash-project's ash_graphql component. An unauthenticated client can send a specially crafted relay node query that triggers an unhandled KeyError, causing the resolver to crash and potentially exposing a stacktrace. This occurs because the type segment of a decoded global ID is not validated before being used as a key in a map fetch operation. The issue affects versions from 0.27.0 up to but not including 1.11.0.

CVE-2026-81643 is an incorrect authorization vulnerability in the ash-project's ash_graphql component. It causes GraphQL subscription payloads to include records that subscribers are not authorized to see due to improper filtering of batched notifications. The issue affects versions from 1.4.0 up to but not including 1.11.0.

Exposure of Data Element to Wrong Session vulnerability in ash-project ash_graphql can deliver one subscription's resolved records to a different subscriber's topic. AshGraphql.Subscription.Batcher.do_send/5 reads the resolved batch from the process dictionary via Process.get(:batch_resolved) and then unconditionally deletes it. That is sound only inside a task the library owns. On the :backpressure_sync and :noproc fallbacks do_send/5 runs inline in the publishing caller's process, so if a resolver inside an outer do_send/5 triggers another synchronous Ash notification, the inner call finds the outer run's value still under :batch_resolved, adopts it as its own result, and publishes it to the inner topic, a different subscription document with a different actor and tenant. It then deletes the key, so the outer run publishes nothing. The key is not namespaced by run, so records cannot be told apart. The fix saves, clears, and restores :batch_resolved around each run. This issue affects ash_graphql: from 1.4.0 before 1.11.0.