CVE-2026-92684: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2026-92684 is a Missing Authentication for Critical Function vulnerability (CWE-306) in the Neo4j @neo4j/graphql library that allows unauthenticated remote attackers to read protected data via GraphQL aggregation queries. It affects versions 5.0.0 through 5.12.16 and 7.0.0 through 7.6.7 of the npm package. The vulnerability was disclosed on November 10, 2026, with patches released simultaneously. It carries a CVSS v4.0 base score of 8.7 (High) (GitHub Advisory).

Technical details

The root cause is that field-level @authentication directives are not enforced on two categories of GraphQL aggregation queries (CWE-306). First, string aggregates can return stored field values verbatim, bypassing field-level authentication controls that would otherwise deny direct field access. Second, connection-root aggregates bypass an entity's AGGREGATE authentication requirement entirely, allowing unauthenticated callers to obtain aggregate results. No user interaction or privileges are required, and the attack complexity is low, making this exploitable by any network-accessible attacker who can send GraphQL queries to the affected endpoint (GitHub Advisory).

Impact

Successful exploitation allows unauthenticated attackers to read data that is explicitly protected by field-level @authentication controls, resulting in a high confidentiality impact. Sensitive field values can be extracted verbatim through string aggregation queries, and aggregate statistics over protected entities can be obtained through connection-root aggregates. There is no integrity or availability impact; however, exposure of protected data could facilitate further attacks such as credential harvesting or targeted social engineering (GitHub Advisory).

Exploitability

There is no public proof-of-concept exploit code and no evidence of in-the-wild exploitation at the time of disclosure (GitHub Advisory). The EPSS score is approximately 0.40%, indicating a low near-term exploitation probability. The NVD SSVC assessment notes the vulnerability is automatable (no human interaction required) but records exploitation status as "none." The CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.

Exploitation steps

  1. Reconnaissance: Identify applications exposing a Neo4j @neo4j/graphql GraphQL endpoint running versions 5.0.0–5.12.16 or 7.0.0–7.6.7. This can be done via service fingerprinting, reviewing public API documentation, or inspecting GraphQL introspection responses.
  2. Identify protected fields: Use GraphQL introspection (if enabled) or application documentation to identify types and fields that are expected to be protected by @authentication directives.
  3. Craft string aggregate query: Send an unauthenticated GraphQL query using a string aggregate operation (e.g., { usersAggregate { name { shortest longest } } }) targeting a field protected by @authentication. The library fails to enforce the authentication check, returning stored values verbatim.
  4. Craft connection-root aggregate query: Alternatively, send an unauthenticated GraphQL query using a connection-root aggregate (e.g., { usersConnection { aggregate { count } } }) against an entity with an AGGREGATE authentication requirement. The library bypasses the requirement and returns aggregate results.
  5. Exfiltrate data: Iterate over aggregation queries to enumerate protected field values or statistical information, potentially reconstructing sensitive records from aggregate outputs (GitHub Advisory).

Indicators of compromise

  • Network: Unusual or high-volume unauthenticated GraphQL POST requests to the application's GraphQL endpoint containing Aggregate or Connection operation names or fields (e.g., usersAggregate, postsConnection { aggregate }) without accompanying authentication headers or tokens.
  • Logs: Application or API gateway logs showing repeated GraphQL queries with aggregation operations (*Aggregate, *Connection) from unauthenticated sessions or anonymous users; absence of Authorization headers in requests that return aggregate data for protected types.
  • Application Behavior: Aggregate query responses returning data for fields that should be restricted, observable via API monitoring or response logging middleware.

Mitigation and workarounds

Upgrade @neo4j/graphql to version 5.12.17 (LTS) or 7.6.8 (latest) to fully remediate the vulnerability (GitHub Advisory). As an interim workaround prior to patching, restrict access to aggregate queries over protected data at the application or API gateway level — for example, by blocking or rate-limiting GraphQL operations containing Aggregate or connection-root aggregate fields for unauthenticated users. Additionally, consider disabling GraphQL introspection in production environments to reduce attacker reconnaissance capability.

Additional resources


Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-133212CRITICAL9
  • JavaScript logoJavaScript
  • @fastify/reply-from
NoYesNov 20, 2026
GHSA-g84f-3cfw-8wx9HIGH7.6
  • JavaScript logoJavaScript
  • @mikro-orm/knex
NoYesNov 20, 2026
GHSA-f5wg-pmm4-pj63MEDIUM5.4
  • JavaScript logoJavaScript
  • @mikro-orm/core
NoYesNov 20, 2026
GHSA-xf7r-48j6-xg78MEDIUM5.3
  • JavaScript logoJavaScript
  • pnpm
NoNoNov 20, 2026
GHSA-m7x9-2hqg-jvqxMEDIUM4.3
  • JavaScript logoJavaScript
  • @mikro-orm/core
NoYesNov 20, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management