{"answers":{"affected":"1 open source package ship an affected version, including ash_graphql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81636 exists.","fix":"Upgrade ash_graphql to 1.11.0 or later.","what":"CVE-2026-81636 is a high-severity denial of service vulnerability in ash-project ash_graphql, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81636 and fix it if it is affected.\n\nWhat it is: CVE-2026-81636 is a high-severity denial of service vulnerability in ash-project ash_graphql, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81636 exists.\n\nAffected packages and fixed versions:\n- ash_graphql (Hex): affected from 0.16.23; fixed in 1.11.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81636/ (Markdown: https://insights.sbomify.com/CVE-2026-81636/index.md)","id":"CVE-2026-81636","markdown":"https://insights.sbomify.com/CVE-2026-81636/index.md","name":"CVE-2026-81636","record":{"aliases":["EEF-CVE-2026-81636","GHSA-mwc4-r9fc-h6mg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir GraphQL library","requires_auth":"none","summary":"Unauthenticated attackers can bypass query complexity limits in AshGraphql to force unbounded database reads, causing denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.\n\nAshGraphql.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.\n\nThis issue affects ash_graphql: from 0.16.23 before 1.11.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Query-complexity limit bypass via first/last pagination arguments in AshGraphql enables denial of service","id":"CVE-2026-81636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Replayable OAuth2 CSRF state retained after a failed callback in AshAuthentication","id":"CVE-2026-81637"},"packages":[{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["0.16.23"],"last_affected":[],"package":"ash_graphql","purl":"pkg:hex/ash_graphql","source":"EEF-CVE-2026-81636"}],"prev":{"headline":"Cross-site scripting in SHIRASAGI","id":"CVE-2026-81635"},"products":["ash_graphql"],"published":"2026-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Unauthenticated attackers can bypass query complexity limits in AshGraphql to force unbounded database reads, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-81636/"}