CVE-2026-81643
Last modified
CVE-2026-81643 is a low-severity vulnerability rated 2.3/10 on the CVSS scale. 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. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| ash-project | ash_graphql | >= 1.4.0, < 1.11.0 |
| ash-project | ash_graphql | >= 3cb2c9870d050c7c4bba6c211aaed97d732f7e81, < e8e67f39add2ce0771e6db5f086afe68ba212c57 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-81643?
How severe is CVE-2026-81643?
How do I fix CVE-2026-81643?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-81636Allocation of Resources Without Limits or Throttling vulnera…8.7
- CVE-2026-81637Insufficient Session Expiration vulnerability in team-alembi…2.3
- CVE-2026-81638Improper Handling of Alternate Encoding vulnerability in ash…2.1
- CVE-2026-8164Uncontrolled Search Path Element vulnerability in ArkSigner …7.3
- CVE-2026-81640An attacker could derive the camera's Wi-Fi password and con…8.8
- CVE-2026-81642In NLnet Labs Unbound up to and including 1.26.0, a vulnerab…9.8
- CVE-2026-81644DoS vulnerability in the preview service module. Impact: Suc…4.3
- CVE-2026-81645Out-of-bounds read vulnerability in the graphics module. Suc…5.9
- CVE-2026-81646Out-of-bounds read vulnerability in the graphics module. Imp…5.9
- CVE-2026-81647Out-of-bounds read vulnerability in the graphics module. Imp…5.3
- CVE-2026-81648The CryptoPayment Gateway WordPress plugin from 1.2.1 to 1.2…10
- CVE-2026-81649The Fundiin cho WooCommerce WordPress plugin through 3.4.0 d…9.1
Are you affected by CVE-2026-81643?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
