Public vulnerability disclosure

CVE-2026-92684

Aggregation queries can bypass authentication restrictions in @neo4j/graphql

publishedCWE-306

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.

Technical severity8.7 highCVSS 4.0 · CNA: Neo4j
Published2026-11-10Source updated 2026-11-10
Collected2026-11-101 attributed source

Fixes and workarounds

Fix

Upgrade @neo4j/graphql to 7.6.8 (latest) or 5.12.17 (LTS).

Source: CNA: Neo4j

Workaround

Restrict access to aggregate queries over protected data until the upgrade is applied.

Source: CNA: Neo4j

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
@neo4j/graphql
Neo4j
@neo4j/graphql
https://registry.npmjs.org
≥ 5.0.0; < 5.12.17 (affected, semver)
≥ 7.0.0; < 7.6.8 (affected, semver)
Other versions: unaffected
CNA: Neo4j

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
4.0 / 8.7
high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCNA: Neo4j

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide