CVE-2026-81636
Unauthenticated GraphQL pagination bug bypasses complexity limits, enabling unbounded DB reads.
Is CVE-2026-81636 being exploited?
Not confirmed. CVE-2026-81636 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-81636?
CVE-2026-81636 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-81636?
Yes. A fix has been recorded for CVE-2026-81636. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-81636 affect?
CVE-2026-81636 affects ash_graphql >=0.16.23 and <1.11.0, Elixir apps using ash_graphql, GraphQL APIs built with Ash/AshGraphql. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-81636?
Upgrade ash_graphql to >=1.11.0 or apply the vendor patch immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can bypass query-complexity limits via relay pagination (first/last), forcing large/unbounded DB reads causing DoS and large data retrieval.
Immediate action required
- affected>= 0.16.23 and < 1.11.0
- affected>= d8a3e1b15587180ad9cb3ceeb398863d086c163b and < c3229f6a65cbabb32fd7ffcac881922d1b3b30ad
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.