Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-92684

Aggregation queries can bypass authentication restrictions in @neo4j/graphql

Products / packages Neo4j @neo4j/graphql

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:30:31 UTC
Neo4j · CVSS:4.0 · 8.7
Assessment vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Severity

high8.7

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

In @neo4j/graphql versions 5.0.0 before 5.12.17 and 7.0.0 before 7.6.8, aggregation queries can bypass authentication restrictions, allowing attackers to read protected data. Field-level authentication is not enforced on string aggregates. This weakness may allow unauthenticated callers to obtain aggregate results.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Neo4j · Neo4j

@neo4j/graphql

2 ranges
Neo4j version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

5.0.0 → before 5.12.17

semver versions

7.0.0 → before 7.6.8

semver versions

unaffected

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

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

Neo4j guidance ↗

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

Neo4j guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

1 sources
neo4j/graphql · security/advisories/GHSA-9r8x-hf5g-rh66
Vendor advisoryNeo4j

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-92684

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-306 ↗

CWE-306 Missing Authentication for Critical Function

Neo4j

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Neo4j · platform conditions

Any condition may hold

Any condition may hold

Vulnerable product

cpe:2.3:a:neo4j:_neo4j_graphql:*:*:*:*:*:*:*:*

From (inclusive): 5.0.0

Before: 5.12.17

Vulnerable product

cpe:2.3:a:neo4j:_neo4j_graphql:*:*:*:*:*:*:*:*

From (inclusive): 7.0.0

Before: 7.6.8

Applicability preview
[
  {
    "operator": "OR",
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:neo4j:_neo4j_graphql:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0.0",
            "versionEndExcluding": "5.12.17"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:neo4j:_neo4j_graphql:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "7.0.0",
            "versionEndExcluding": "7.6.8"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Neo4j

Assigning organization

2026-11-10

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.