Quick answers
- Is CVE-2026-92684 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92684 being exploited in the wild.
- How severe is CVE-2026-92684?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Neo4j @Neo4j/Graphql 5.0.0 before 5.12.17; 7.0.0 before 7.6.8.
- Is there a fix for CVE-2026-92684?
- Yes: fixed in 5.12.17, 7.6.8. Until then: Restrict access to aggregation queries over protected data until the library is upgraded to a patched version. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92684 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92684?
- Check whether you run Neo4j @Neo4j/Graphql at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.12.17, 7.6.8
Restrict access to aggregation queries over protected data until the library is upgraded to a patched version.
Technical details
The @neo4j/graphql library fails to enforce field-level @authentication decorators on string aggregates and connection-root aggregates. String aggregates return stored values verbatim without checking authentication, and connection-root aggregates bypass entity AGGREGATE authentication entirely. This is a network-accessible, unauthenticated attack requiring no user interaction.
Affected products
- Neo4j @neo4j/graphql 5.0.0 before 5.12.17; 7.0.0 before 7.6.8
Timeline
- 2026-11-10: disclosed