CVE-2026-92684 · Package
NO FIX YET · SEE WHAT TO DO
The @neo4j/graphql library skips field-level authentication on string aggregates and lets connection-root aggregates bypass the entity's AGGREGATE authentication rule. A remote caller can read protected stored values and aggregate results without logging in.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that expose a GraphQL API built on @neo4j/graphql and use @authentication rules to protect data. The exposure comes from the aggregation query path, so apps that never expose aggregation queries, or that restrict the API to authenticated callers at the gateway, are less exposed. The sources do not say which default configuration is affected.
Not affected if auth-enforced-at-gateway, no-aggregation-queries
Who cares graphql, neo4j, node.js, self-hosted
npm ls @neo4j/graphql@authentication rules on types that use string fields or aggregation queries in your GraphQL schema@neo4j/graphql 5.x: move to 5.12.17 or later@neo4j/graphql 7.x: move to 7.6.8 or laterMissing 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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.