CVE-2026-92682 (GCVE-0-2026-92682)
Vulnerability from cvelistv5 – Published: 2026-10-12 15:07 – Updated: 2026-10-12 15:07
VLAI
EPSS
VEX
Title
@neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier
Summary
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.
Severity
CWE
- CWE-863 - Incorrect Authorization
Assigner
References
4 references
| URL | Tags |
|---|---|
| https://github.com/neo4j/graphql/security/advisor… | vendor-advisory |
| https://github.com/neo4j/graphql/commit/17650cc37… | patch |
| https://github.com/neo4j/graphql/releases/tag/%40… | release-notes |
| https://www.npmjs.com/package/@neo4j/graphql | product |
Impacted products
1 product
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Neo4j | @neo4j/graphql |
Affected:
7.0.0 , < 7.6.4
(semver)
|
guessed |
{
"containers": {
"cna": {
"affected": [
{
"collectionURL": "https://registry.npmjs.org",
"defaultStatus": "unaffected",
"packageName": "@neo4j/graphql",
"product": "@neo4j/graphql",
"repo": "https://github.com/neo4j/graphql",
"vendor": "Neo4j",
"versions": [
{
"lessThan": "7.6.4",
"status": "affected",
"version": "7.0.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Neo4j Application Security team"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "In @neo4j/graphql versions from 7.0.0 up to but not including 7.6.4, the \u003ccode\u003enone\u003c/code\u003e quantifier in \u003ccode\u003e@authorization\u003c/code\u003e filters on relationships and connections is not negated when translated to Cypher, so it behaves like \u003ccode\u003esome\u003c/code\u003e. 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\u0027t have access according to the typedefs. Fixed in 7.6.4."
}
],
"value": "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\u0027t have access according to the typedefs. Fixed in 7.6.4."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-863",
"description": "CWE-863 Incorrect Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-12T15:07:44.638Z",
"orgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"shortName": "Neo4j"
},
"references": [
{
"name": "GHSA-h873-p2wr-fjx6",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/neo4j/graphql/security/advisories/GHSA-h873-p2wr-fjx6"
},
{
"name": "Fix commit 17650cc",
"tags": [
"patch"
],
"url": "https://github.com/neo4j/graphql/commit/17650cc370445a6bb9d394d34063d3623e987aa2"
},
{
"name": "@neo4j/graphql 7.6.4 release notes",
"tags": [
"release-notes"
],
"url": "https://github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4"
},
{
"tags": [
"product"
],
"url": "https://www.npmjs.com/package/@neo4j/graphql"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade @neo4j/graphql to version 7.6.4 or later.\u003c/p\u003e"
}
],
"value": "Upgrade @neo4j/graphql to version 7.6.4 or later."
}
],
"source": {
"discovery": "INTERNAL"
},
"title": "@neo4j/graphql: authorization relationship and connection filters invert the \"none\" quantifier",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAvoid the none quantifier in @authorization relationship and connection filters until you can upgrade, and verify any replacement rule with tests that cover both denied and allowed users.\u003c/p\u003e"
}
],
"value": "Avoid the none quantifier in @authorization relationship and connection filters until you can upgrade, and verify any replacement rule with tests that cover both denied and allowed users."
}
],
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"assignerShortName": "Neo4j",
"cveId": "CVE-2026-92682",
"datePublished": "2026-10-12T15:07:44.638Z",
"dateReserved": "2026-09-16T16:17:17.929Z",
"dateUpdated": "2026-10-12T15:07:44.638Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-92682",
"date": "2026-10-13",
"epss": "0.00313",
"percentile": "0.22455"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://registry.npmjs.org",
"defaultStatus": "unaffected",
"packageName": "@neo4j/graphql",
"product": "@neo4j/graphql",
"repo": "https://github.com/neo4j/graphql",
"vendor": "Neo4j",
"versions": [
{
"lessThan": "7.6.4",
"status": "affected",
"version": "7.0.0",
"versionType": "semver"
}
]
}
],
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027t have access according to the typedefs. Fixed in 7.6.4."
}
],
"id": "CVE-2026-92682",
"lastModified": "2026-10-12T16:17:07.480",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"type": "Secondary"
}
]
},
"published": "2026-10-12T16:17:07.480",
"references": [
{
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"url": "https://github.com/neo4j/graphql/commit/17650cc370445a6bb9d394d34063d3623e987aa2"
},
{
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"url": "https://github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4"
},
{
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"url": "https://github.com/neo4j/graphql/security/advisories/GHSA-h873-p2wr-fjx6"
},
{
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"url": "https://www.npmjs.com/package/@neo4j/graphql"
}
],
"sourceIdentifier": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-863"
}
],
"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"type": "Secondary"
}
]
}
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…