{"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-80223 exists.","fix":"Upgrade ash_graphql to 1.11.0 or later.","what":"CVE-2026-80223 is a high-severity missing authorization vulnerability in ash-project ash_graphql, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80223 and fix it if it is affected.\n\nWhat it is: CVE-2026-80223 is a high-severity missing authorization vulnerability in ash-project ash_graphql, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80223 exists.\n\nAffected packages and fixed versions:\n- ash_graphql (Hex): affected from 1.4.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-80223/ (Markdown: https://insights.sbomify.com/CVE-2026-80223/index.md)","id":"CVE-2026-80223","markdown":"https://insights.sbomify.com/CVE-2026-80223/index.md","name":"CVE-2026-80223","record":{"aliases":["EEF-CVE-2026-80223","GHSA-rcqc-59g2-gjg2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir GraphQL library","requires_auth":"low_privilege","summary":"Authenticated users in one tenant can receive another tenant's records via GraphQL subscriptions due to missing tenant-scoped authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Incorrect Authorization vulnerability in ash-project ash_graphql allows an authenticated subscriber in one tenant to receive another tenant's records over GraphQL subscriptions.\n\nThe subscription resolver in AshGraphql.Graphql.Resolver authorizes each notification payload in memory: its fast path calls Ash.can/3 with run_queries?: false, which evaluates the read policy filter against the in-memory record via Ash.Expr.eval/2 and never issues a query. Ash applies multitenancy at query-build and data-layer-prefix time, not inside query.filter, so the evaluated policy carries no tenant condition and a tenant-B notification routed to a tenant-A subscriber is emitted whenever the policy filter is true. The single-notification clause has no tenant guard at all, and the batched clause checks only the head of the notification list, so non-head entries authorize purely in memory. A tenant-scoped read is reached only when filter evaluation fails.\n\nThis issue affects ash_graphql: from 1.4.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":"Cross-tenant subscription disclosure in AshGraphql authorizes notifications in memory without a tenant-scoped read","id":"CVE-2026-80223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Possible degradation of service from continuous queries on the same TCP/DoT connection","id":"CVE-2026-80225"},"packages":[{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["1.4.0"],"last_affected":[],"package":"ash_graphql","purl":"pkg:hex/ash_graphql","source":"EEF-CVE-2026-80223"}],"prev":{"headline":"Red Hat Product Security has come to the conclusion that this CVE is not needed.","id":"CVE-2026-80219"},"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Authenticated users in one tenant can receive another tenant's records via GraphQL subscriptions due to missing tenant-scoped authorization checks.","url":"https://insights.sbomify.com/CVE-2026-80223/"}