Read the docs

Aggregation queries can bypass authentication restrictions in @neo4j/graphql

Priority MEDIUM 44CWE-306Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-306.

Summary

Neo4j @neo4j/graphql from 5.0.0 before 5.12.17 and from 7.0.0 before 7.6.8 is affected. Missing authentication for a critical function (CWE-306) lets aggregation queries skip authentication checks. Field-level @authentication is not enforced on string aggregates, which can return stored values verbatim, and connection-root aggregates bypass an entity's AGGREGATE authentication requirement. A remote unauthenticated attacker can read protected data through GraphQL aggregation queries.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

Missing Authentication for Critical Function in aggregation queries in Neo4j @neo4j/graphql 5.0.0 before 5.12.17 and 7.0.0 before 7.6.8 allows remote attackers to read protected data via GraphQL aggregation queries. Field-level @authentication is not enforced on string aggregates, which can return stored values verbatim, and connection-root aggregates bypass an entity's AGGREGATE authentication requirement, allowing unauthenticated callers to obtain aggregate results.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00401 34th percentileScored 2026-11-16
Fix Fixed @neo4j/graphql (Neo4j): 5.12.17, 7.6.8

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
neo4j@neo4j/graphql5.0.0 to before 5.12.17; 7.0.0 to before 7.6.85.12.17, 7.6.8Patch availableCNA
  • @neo4j/graphql Vendorneo4j Affected 5.0.0 to before 5.12.17; 7.0.0 to before 7.6.8 Fixed in 5.12.17, 7.6.8 Patch available CNA

Remediation

Upgrade @neo4j/graphql to version 5.12.17 or 7.6.8, which fix the flaw in the 5.x and 7.x branches respectively. The sources list no fixed version for any other release line.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA @neo4j/graphql (Neo4j) Fixed in 5.12.17, 7.6.8

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-92684
  2. 2026-11-12 Priority changed: MEDIUM → LOW
  3. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2021-13406 Neo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that… CVSS 3.1CRITICAL 9.8
  • TI-2026-71015 Authentication ignored for top-level @cypher fields in @neo4j/graphql CVSS 4.0CRITICAL 9.3
  • TI-2018-16042 neo4j-contrib neo4j-apoc-procedures version before commit 45bc09c contains a XML External… CVSS 3.0CRITICAL 10.0
  • TI-2018-13005 Due to incorrect access control in Neo4j Enterprise Database Server 3.4.x before 3.4.9… CVSS 3.0CRITICAL 9.8
  • TI-2021-18971 A directory traversal vulnerability in the apoc plugins in Neo4J Graph database before… CVSS 3.1CRITICAL 9.1
  • TI-2026-87034 Incorrect authorization in Neo4j @neo4j/graphql JWT filters CVSS 4.0HIGH 8.6
See all 24 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences