EEF-CVE-2026-81633
- Source
- https://cna.erlef.org/osv/EEF-CVE-2026-81633.html
- Import Source
- https://cna.erlef.org/osv/EEF-CVE-2026-81633.json
- JSON Data
- https://api.osv.dev/v1/vulns/EEF-CVE-2026-81633
- Aliases
-
- CVE-2026-81633
- GHSA-mrgv-g7gf-r96h
- Published
- 2026-08-30T18:22:07.096Z
- Modified
- 2026-08-30T18:25:38.208616322Z
- Severity
-
- 6.9 (Medium) CVSS_V4 - 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 CVSS Calculator
- Summary
- Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment
- Details
-
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.
- Database specific
{ "cpe_ids": [ "cpe:2.3:a:ash-project:ash_graphql:*:*:*:*:*:*:*:*" ], "capec_ids": [ "CAPEC-153" ], "cwe_ids": [ "CWE-20" ] }- References
- Credits
-
-
- Peter Ullrich - FINDER
-
- Peter Ullrich - REPORTER
-
- Zach Daniel / Ash Project - REMEDIATION_DEVELOPER
-
- Jonatan Männchen / EEF - COORDINATOR
-
Affected packages
Hex / ash_graphql
Package
- Name
- ash_graphql
- Purl
- pkg:hex/ash_graphql