CVE-2026-92682 @neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier
Authenticated users can bypass authorization filters to read, create, or delete protected records due to inverted logic in relationship filters.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-92682?
CVE-2026-92682 is a high-severity missing authorization vulnerability in @neo4j/graphql, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-863
Which versions are affected by CVE-2026-92682?
How do I fix CVE-2026-92682?
No fix has been published for CVE-2026-92682 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-92682 being exploited?
There is no known exploitation of CVE-2026-92682 in the wild and no public exploit code.
Sources
Also known as GHSA-h873-p2wr-fjx6.