Data disclosure via missing aggregation authentication checks
Published Nov 10, 2026 · Updated Nov 10, 2026
Authentication bypass in Neo4j GraphQL Library allows remote attackers to read protected data through aggregation queries. String aggregates ignore field-level @authentication and return stored values verbatim, while connection-root aggregates bypass entity-level AGGREGATE authentication. Exposure requires reachable aggregation queries over protected data; unauthenticated callers obtain values or aggregate results despite direct-query restrictions.
Summary
What happened
Authentication bypass in Neo4j GraphQL Library allows remote attackers to read protected data through aggregation queries. String aggregates ignore field-level @authentication and return stored values verbatim, while connection-root aggregates bypass entity-level AGGREGATE authentication. Exposure requires reachable aggregation queries over protected data; unauthenticated callers obtain values or aggregate results despite direct-query restrictions.
The record
- CVE
- CVE-2026-92684
- Published
- Nov 10, 2026
- Updated
- Nov 10, 2026
- Vendor
- Neo4j
- Product
- Neo4j GraphQL Library
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2026CVE publishedPublication date reported by the CVE source.
- Nov 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.0 <5.12.17
- Affected versionversion=7.0.0 <7.6.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us