CVE-2026-81636
Last modified
CVE-2026-81636 is a high-severity vulnerability rated 8.7/10 on the CVSS scale. Allocation of Resources Without Limits or Throttling vulnerability in ash-project ash_graphql allows an unauthenticated client to bypass the configured GraphQL query-complexity limit and force an unbounded database read. AshGraphql.Graphql.Resolver.query_complexity/3 multiplies child complexity by the requested page size only when the argument map contains :limit (offset pagination). Relay connections and keyset pagination use first and last, which never match that clause and fall through to the catch-all that returns child_complexity + 1. EPSS estimates a 0.34% chance of exploitation in the next 30 days.
Description
Allocation of Resources Without Limits or Throttling vulnerability in ash-project ash_graphql allows an unauthenticated client to bypass the configured GraphQL query-complexity limit and force an unbounded database read. AshGraphql.Graphql.Resolver.query_complexity/3 multiplies child complexity by the requested page size only when the argument map contains :limit (offset pagination). Relay connections and keyset pagination use first and last, which never match that clause and fall through to the catch-all that returns child_complexity + 1. A nested relay query such as posts(first: 500) { edges { node { comments(first: 500) { ... } } } } therefore scores as trivially cheap while materializing the full fan-out, passing an Absinthe max_complexity cap that rejects the equivalent limit-based query. The fix adds first and last clauses clamped to the action's page size. This issue affects ash_graphql: from 0.16.23 before 1.11.0.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| ash-project | ash_graphql | >= 0.16.23, < 1.11.0 |
| ash-project | ash_graphql | >= d8a3e1b15587180ad9cb3ceeb398863d086c163b, < c3229f6a65cbabb32fd7ffcac881922d1b3b30ad |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-81636?
How severe is CVE-2026-81636?
How do I fix CVE-2026-81636?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- 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-8163The Infility Global WordPress plugin before 2.15.19 does not…8.8
- CVE-2026-81630The Botslab G980H dash camera firmware does not adequately v…8.1
- CVE-2026-81632Use of HTTP Request With Sensitive Query String vulnerabilit…7.2
- CVE-2026-81633Improper Input Validation vulnerability in ash-project ash_g…6.9
- CVE-2026-81634In NLnet Labs Unbound up to and including 1.26.0, a 255 leng…7.5
- CVE-2026-81635A cross-site scripting vulnerability exists in SHIRASAGI, wh…5.1
- 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-81643Incorrect Authorization vulnerability in ash-project ash_gra…2.3
Are you affected by CVE-2026-81636?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
