CVE-2026-92682: @neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier
Neo4j · @neo4j/graphql
Vendor fix available · Affected: Neo4j @neo4j/graphql · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 24% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Neo4j · @neo4j/graphqlfrom 7.0.0 before 7.6.4
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Neo4j
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-92682 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.