@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.
CVE-2026-92682
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-92682
@neo4j/graphql
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://github.com/neo4j/graphql",
"vendor": "Neo4j",
"product": "@neo4j/graphql",
"versions": [
{
"status": "affected",
"version": "7.0.0",
"lessThan": "7.6.4",
"versionType": "semver"
}
],
"packageName": "@neo4j/graphql",
"collectionURL": "https://registry.npmjs.org",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-92682
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #32873 · Revision 1
- Added to Heist Feed
- Publisher date