Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade @neo4j/graphql to version 7.6.4 or later.
Workaround
Avoid the none quantifier in @authorization relationship and connection filters until you can upgrade, and verify any replacement rule with tests that cover both denied and allowed users.
Mon, 12 Oct 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | @neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Neo4j
Published:
Updated: 2026-10-12T15:07:44.638Z
Reserved: 2026-09-16T16:17:17.929Z
Link: CVE-2026-92682
No data.
Status : Received
Published: 2026-10-12T16:17:07.480
Modified: 2026-10-12T16:17:07.480
Link: CVE-2026-92682
No data.
OpenCVE Enrichment
Updated: 2026-10-12T17:15:15Z