Quick answers
- Is CVE-2026-92681 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92681 being exploited in the wild.
- How severe is CVE-2026-92681?
- Informational severity, published 12 October 2026.
- Which products and versions are affected?
- Neo4j @Neo4j/Graphql up to and including 7.6.3.
- Is there a fix for CVE-2026-92681?
- Yes: fixed in 7.6.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92681 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92681?
- 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: 7.6.4
Technical details
Authentication directives (@authentication) applied at the schema or Query/Mutation type level are silently bypassed for top-level fields marked with @cypher; only field-level directives are enforced. An unauthenticated attacker can invoke unprotected @cypher fields over the network and execute arbitrary Cypher statements with the GraphQL service account's database privileges. The vulnerability is fixed in version 7.6.4 by consolidating auth handling between custom resolver and @cypher field paths.
Affected products
- Neo4j @neo4j/graphql up to and including 7.6.3
Timeline
- 2026-10-12: disclosed