{"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-81633 exists.","fix":"Upgrade ash_graphql to 1.11.0 or later.","what":"CVE-2026-81633 is a medium-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-81633 and fix it if it is affected.\n\nWhat it is: CVE-2026-81633 is a medium-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-81633 exists.\n\nAffected packages and fixed versions:\n- ash_graphql (Hex): affected from 0.27.0; 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-81633/ (Markdown: https://insights.sbomify.com/CVE-2026-81633/index.md)","id":"CVE-2026-81633","markdown":"https://insights.sbomify.com/CVE-2026-81633/index.md","name":"CVE-2026-81633","record":{"aliases":["EEF-CVE-2026-81633","GHSA-mrgv-g7gf-r96h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir GraphQL library","requires_auth":"none","summary":"An unauthenticated attacker can crash GraphQL queries and potentially expose stack traces by sending a malformed relay node ID with an unknown type segment.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Improper Input Validation vulnerability in ash-project ash_graphql allows an unauthenticated client to crash a relay node(id: ...) query with an unhandled KeyError.\n\nAshGraphql.Graphql.Resolver.resolve_node/2 decodes the client-supplied global ID with decode_relay_id/1, which only base64-decodes the string and splits it on : without validating the type segment. The decoded type is passed straight to Map.fetch!(type_to_domain_and_resource_map, type). Because fetch! raises on a missing key, a relay ID whose type segment is a valid atom that is not a relay-exposed type aborts the resolver before its resolve/2 clauses and their rescue handlers run, so the error never becomes a GraphQL error and may expose a stacktrace. Common resource names are easy to guess. The fix uses Map.fetch/2 and returns an Invalid node id error for unknown types.\n\nThis issue affects ash_graphql: from 0.27.0 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":"Unhandled KeyError in AshGraphql relay node resolution crashes queries via an unknown type segment","id":"CVE-2026-81633","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":"Possible heap buffer overflow during DNSSEC canonicalization","id":"CVE-2026-81634"},"packages":[{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["0.27.0"],"last_affected":[],"package":"ash_graphql","purl":"pkg:hex/ash_graphql","source":"EEF-CVE-2026-81633"}],"prev":{"headline":"Single-use sign-in token placed in a redirect query string in AshAuthenticationPhoenix","id":"CVE-2026-81632"},"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":"An unauthenticated attacker can crash GraphQL queries and potentially expose stack traces by sending a malformed relay node ID with an unknown type segment.","url":"https://insights.sbomify.com/CVE-2026-81633/"}