Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment (CVE-2026-81633) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81633

Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment

Answer in brief

CVE-2026-81633 records a Unknown severity vulnerability in Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_graphql (generic), ash-project/ash_graphql (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 30, 2026Updated Aug 30, 2026Source checked Aug 30, 2026First seen by HOL Aug 30, 2026Material review Aug 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ash-project/ash_graphql (generic), ash-project/ash_graphql (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ash_graphqlgeneric	>=0.27.0 <1.11.0	1.11.0
ash-project/ash_graphqlgeneric	>=365b3aedc6b36f020e6a2c7dce63fa569243bc4e <c8863ed8e5c21f1bfb6125f1d24e78443dfc6351	c8863ed8e5c21f1bfb6125f1d24e78443dfc6351

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash_graphql, ash-project/ash_graphql.
Review the reported fix. Update ash-project/ash_graphql to 1.11.0; ash-project/ash_graphql to c8863ed8e5c21f1bfb6125f1d24e78443dfc6351 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 30, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.