Broken access control in AshGraphql subscription batcher applies authorization suppression to only the first notification (CVE-2026-81643) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81643

Broken access control in AshGraphql subscription batcher applies authorization suppression to only the first notification

Answer in brief

CVE-2026-81643 records a Unknown severity vulnerability in Broken access control in AshGraphql subscription batcher applies authorization suppression to only the first notification. 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	>=1.4.0 <1.11.0	1.11.0
ash-project/ash_graphqlgeneric	>=3cb2c9870d050c7c4bba6c211aaed97d732f7e81 <e8e67f39add2ce0771e6db5f086afe68ba212c57	e8e67f39add2ce0771e6db5f086afe68ba212c57

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 e8e67f39add2ce0771e6db5f086afe68ba212c57 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

Incorrect Authorization vulnerability in ash-project ash_graphql delivers GraphQL subscription payloads for records a subscriber is not authorized to see. In AshGraphql.Subscription.Batcher, do_send/5 resolves the first notification of a batch and filters it with should_send?/1, which drops results whose errors are coded forbidden or not_found or carry no code, precisely so that unauthorized results are not disclosed. The remaining notifications in the batch are read from the process dictionary, re-run through the pipeline, and appended to the outgoing results without that filter. They reach pubsub.publish_subscription/2, and the not is_nil(record) guard drops only nil records, not error-carrying results. Any two qualifying notifications arriving within the default one-second batch interval suffice, and batching is the default path. The fix applies should_send?/1 to the whole batch. This issue affects ash_graphql: from 1.4.0 before 1.11.0.

Quoted source text, attributed separately from HOL analysis.