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.
CVSS
No CVSS.
References
Configurations
No configuration.
History
12 Oct 2026, 16:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-12 16:17
Updated : 2026-10-16 19:55
NVD link : CVE-2026-92682
Mitre link : CVE-2026-92682
CVE.ORG link : CVE-2026-92682
JSON object : View
Products Affected
No product.
CWE
CWE-863
Incorrect Authorization
