6 matches found
CVE-2026-78693
ash_graphql (ash-project, Elixir/Erlang) is vulnerable to incomplete error-message redaction . In AshGraphql.Errors, the configured error_handler output is merged with the pre-handler path via Map.put_new(handled, :path, path), which re-injects the original path even when a sanitizing handler rem...
CVE-2026-80223
ash_graphql (Elixir GraphQL binding for the Ash framework) contains a cross-tenant subscription disclosure in its subscription resolver (AshGraphql.Graphql.Resolver). The fast path calls Ash.can/3 with run_queries?: false, evaluating the read policy filter in memory via Ash.Expr.eval/2 without is...
CVE-2026-81636
ash_graphql (ash-project) versions 0.16.23 through before 1.11.0 contain an allocation-of-resources flaw that lets an unauthenticated client bypass the configured GraphQL query-complexity limit. The root cause is in AshGraphql.Graphql.Resolver.query_complexity/3, which multiplies child complexity...
CVE-2026-81633
CVE-2026-81633 is an improper input validation vulnerability in ash-project ash_graphql (Elixir GraphQL library). The function resolve_node/2 base64-decodes a client-supplied global ID and passes the type segment directly to Map.fetch!/2, which raises an unhandled KeyError when the type is not a ...
CVE-2026-81643
CVE-2026-81643 is a broken access control flaw in ash_graphql (versions 1.4.0 through 1.10.0 ). In AshGraphql.Subscription.Batcher, the should_send?/1 authorization filter is applied only to the first notification in a batch; remaining notifications are appended to outgoing results without that f...
CVE-2026-82367
CVE-2026-82367 is a re-entrant data-exposure bug in ash_graphql (ash-project), affecting versions 1.4.0 through before 1.11.0 . The root cause lies in AshGraphql.Subscription.Batcher.do_send/5, which reads and deletes the process-dictionary key :batch_resolved without namespacing it per run. On t...