CVE-2026-92682@neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier

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

8.6 HIGH (v4.0, CNA)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

Weakness (CWE)

CWE-863

Known exploited

Not in CISA's KEV catalog

EPSS (exploitation in the next 30 days)

0.31% (percentile 23)

Assigned by

Neo4j

NVD analysis

Awaiting Analysis

Record last updated

Oct 16, 2026

First seen by InfoSec Signals

Oct 12, 2026

The CVE record on cve.org · NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.