CVE-2026-92682
In @neo4j/graphql versions from 7.0.0 up to but not including 7.6.4, the none quantifier in…
- Risk score
- 56/100
- CVSS
- 8.6 v4.0
- Exploit chance (30 days)
- 0.3%
- Published
- 12 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 …
- Affected
- See advisory
- Fix
- Upgrade the product to 7.6.4 or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 8.6 high
References
Original 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.
Last activity 12 Oct 2026. Patch Forecast updates every hour.