CVE-2026-92682
In @neo4j/graphql versions from 7.0.0 up to but not including …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/neo4j/graphql/commit/17650cc370445a6bb9d394d34063d3623e987aa2
- github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4
- github.com/neo4j/graphql/security/advisories/GHSA-h873-p2wr-fjx6
- www.npmjs.com/package/@neo4j/graphql
- nvd.nist.gov/vuln/detail/CVE-2026-92682
- cve.org/CVERecord?id=CVE-2026-92682
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.