CVE-2026-92683

Incomplete evaluation of multi-condition JWT where filter in @authentication in @neo4j/graphql

  • High 8.6

Description

Incorrect authorization in the @authentication directive JWT where filter evaluation in Neo4j @neo4j/graphql versions 7.0.0 before 7.6.7 allows an attacker holding an otherwise-valid JWT to bypass all but the first filter condition via a multi-condition jwt where filter written in generic operator syntax.

Key facts

Published
9 Nov 2026
Last changed
12 Nov 2026
Assigned by
Neo4j
EPSS
0.477% likely to be exploited in the next 30 days, higher than 41.776% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.6CVSS 4.0, Highfrom the CNA (Neo4j)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

What to do

  • Upgrade @neo4j/graphql to version 7.6.7 or later.CNA solution statement
  • For versions prior to 7.6.7, express multi-condition jwt where filters either with an explicit AND array (for example jwt: { AND: [{ iss: { eq: "https://idp.example.com" } }, { roles: { includes: "admin" } }] }) or with the inline operator syntax (for example roles_INCLUDES: "admin"). Both forms evaluate all conditions.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

Authorization bypass: JWT claim requirements beyond the first condition (such as a required role) are not enforced, allowing access to data or operations protected by @authentication. (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Neo4j@neo4j/graphql
  • Default status: unaffected
  • 7.0.0 up to but excluding 7.6.7 (affected)

Timeline

  1. 9 Nov 2026 Published

Weakness

References