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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.12.17, 7.6.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.12.17, 7.6.8.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 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
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects npm packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
Impact
- Widely used
@neo4j/graphql has 47.9k weekly downloads.Source: npmjs.com
What to do
Upgrade to a fixed version: 5.12.17, 7.6.8.
Workaround: Restrict access to aggregate queries over protected data until the upgrade is applied.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
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.
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-92684
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: cve.now feed data
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: github.com, cve.org
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: cve.now feed data
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: github.com, cve.org
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: github.com, cve.org