{"affected":[{"package":{"ecosystem":"Hex","name":"ash_graphql","purl":"pkg:hex/ash_graphql"},"ranges":[{"events":[{"introduced":"0.27.0"},{"fixed":"1.11.0"}],"type":"SEMVER"}],"versions":["0.27.0","0.27.1","0.28.0","0.28.1","1.0.0-rc.0","1.0.0-rc.1","1.0.0-rc.2","1.0.0-rc.3","1.0.0-rc.4","1.0.0-rc.5","1.0.0","1.0.1","1.1.0","1.1.1","1.2.0","1.2.1","1.3.0","1.3.1","1.3.2","1.3.3","1.3.4","1.4.0","1.4.1","1.4.2","1.4.3","1.4.4","1.4.5","1.4.6","1.4.7","1.5.0","1.5.1","1.6.0","1.7.0","1.7.1","1.7.2","1.7.3","1.7.4","1.7.5","1.7.6","1.7.7","1.7.8","1.7.9","1.7.10","1.7.11","1.7.12","1.7.13","1.7.14","1.7.15","1.7.16","1.7.17","1.8.0","1.8.1","1.8.2","1.8.3","1.8.4","1.8.5","1.9.0","1.9.1","1.9.2","1.9.3","1.9.4","1.10.0","1.10.1"]},{"ranges":[{"events":[{"introduced":"365b3aedc6b36f020e6a2c7dce63fa569243bc4e"},{"fixed":"c8863ed8e5c21f1bfb6125f1d24e78443dfc6351"}],"repo":"https://github.com/ash-project/ash_graphql","type":"GIT"}]}],"aliases":["GHSA-mrgv-g7gf-r96h","CVE-2026-81633"],"credits":[{"name":"Peter Ullrich","type":"FINDER"},{"name":"Peter Ullrich","type":"REPORTER"},{"name":"Zach Daniel / Ash Project","type":"REMEDIATION_DEVELOPER"},{"name":"Jonatan Männchen / EEF","type":"COORDINATOR"}],"database_specific":{"capec_ids":["CAPEC-153"],"cpe_ids":["cpe:2.3:a:ash-project:ash_graphql:*:*:*:*:*:*:*:*"],"cwe_ids":["CWE-20"]},"details":"## Summary\n\nImproper Input Validation vulnerability in ash-project ash\\_graphql allows an unauthenticated client to crash a relay node(id: ...) query with an unhandled KeyError.\n\nAshGraphql.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.\n\nThis issue affects ash\\_graphql: from 0.27.0 before 1.11.0.","id":"EEF-CVE-2026-81633","modified":"2026-08-30T18:22:07.938053Z","published":"2026-08-30T18:22:07.096Z","references":[{"type":"ADVISORY","url":"https://github.com/ash-project/ash_graphql/security/advisories/GHSA-mrgv-g7gf-r96h"},{"type":"WEB","url":"https://cna.erlef.org/cves/CVE-2026-81633.html"},{"type":"FIX","url":"https://github.com/ash-project/ash_graphql/commit/c8863ed8e5c21f1bfb6125f1d24e78443dfc6351"},{"type":"PACKAGE","url":"https://hex.pm/packages/ash_graphql"}],"related":[],"schema_version":"1.7.3","severity":[{"score":"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","type":"CVSS_V4"}],"summary":"Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment","upstream":[]}