CVE-2026-92682

@neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier

Published Oct 12, 2026 CVSS 4.0 · 8.6 High EPSS < 1% KEV · Not listed
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.

Remediation

Vendor Solution

Upgrade @neo4j/graphql to version 7.6.4 or later.


Vendor 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.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Neo4j
Neo4j graphql
Vendors & Products Neo4j
Neo4j graphql
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

{'score': 8.6, '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Neo4j
Published
Updated
Oct 16, 2026, 5:27 PM
Reserved
Sep 16, 2026, 4:17 PM
Status
Awaiting Analysis
Published
Oct 12, 2026, 4:17 PM
Modified
Oct 16, 2026, 7:55 PM