{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92682 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92682 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92682 is a high-severity missing authorization vulnerability in @neo4j/graphql, published on 12 Oct 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-92682 and fix it if it is affected.\n\nWhat it is: CVE-2026-92682 is a high-severity missing authorization vulnerability in @neo4j/graphql, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92682 in the wild and no public exploit code.\n\nAffected product: @neo4j/graphql. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-92682/ (Markdown: https://insights.sbomify.com/CVE-2026-92682/index.md)","id":"CVE-2026-92682","markdown":"https://insights.sbomify.com/CVE-2026-92682/index.md","name":"CVE-2026-92682","record":{"aliases":["GHSA-h873-p2wr-fjx6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GraphQL authorization library","requires_auth":"low_privilege","summary":"Authenticated users can bypass authorization filters to read, create, or delete protected records due to inverted logic in relationship filters.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Neo4j","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In @neo4j/graphql versions from 7.0.0 up to but not including 7.6.4, the none quantifier in @authorization filters on relationships and connections is not negated when translated to Cypher, so it behaves like some. A rule such as \"none of the related denied users matches the JWT subject\" therefore returns exactly the records it was meant to exclude, and excludes those it was meant to return. An authenticated user whom such a rule is meant to deny can read the protected records. This is also the case for mutations, so the impact is that sensitive data could also be created and deleted by users that shouldn't have access according to the typedefs. Fixed in 7.6.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"@neo4j/graphql: authorization relationship and connection filters invert the \"none\" quantifier","id":"CVE-2026-92682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Sulu: JCR-SQL2 injection via `categories` query parameter (unauthenticated)","id":"CVE-2026-92692"},"packages":[],"prev":{"headline":"@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields","id":"CVE-2026-92681"},"products":["@neo4j/graphql"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Neo4j"]},"summary":"Authenticated users can bypass authorization filters to read, create, or delete protected records due to inverted logic in relationship filters.","url":"https://insights.sbomify.com/CVE-2026-92682/"}