Vulnerability advisory
EEF-CVE-2026-81633
Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment
Also known as CVE-2026-81633GHSA-mrgv-g7gf-r96h
- CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/ash-project/ash_graphql ↗ | |
| 365b3aedc6b36f020e6a2c7dce63fa569243bc4e to before c8863ed8e5c21f1bfb6125f1d24e78443dfc6351 | c8863ed8e5c21f1bfb6125f1d24e78443dfc6351 |
Also listed as affected (60)
| |
Description
Summary
Improper Input Validation vulnerability in ash-project ash_graphql allows an unauthenticated client to crash a relay node(id: ...) query with an unhandled KeyError.
AshGraphql.Graphql.Resolver.resolve_node/2 decodes the client-supplied global ID with decode_relay_id/1, which only base64-decodes the string and splits it on : without validating the type segment. The decoded type is passed straight to Map.fetch!(type_to_domain_and_resource_map, type). Because fetch! raises on a missing key, a relay ID whose type segment is a valid atom that is not a relay-exposed type aborts the resolver before its resolve/2 clauses and their rescue handlers run, so the error never becomes a GraphQL error and may expose a stacktrace. Common resource names are easy to guess. The fix uses Map.fetch/2 and returns an Invalid node id error for unknown types.
This issue affects ash_graphql: from 0.27.0 before 1.11.0.