Incomplete evaluation of multi-condition JWT where filter in @authentication in @neo4j/graphql
- Exploited
- No known exploitation
- Fix
- Fixed in 7.6.7
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 7.6.7.
- Last modified
- 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? →
- 27/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? →
- Specific setups only
- 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.
- 61% of @neo4j/graphql downloads last week were affected versions (38.4K).npm, 62.8K downloads in the last 7 days, read Nov 9, 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
Neo4j's @neo4j/graphql library, in versions 7.0.0 before the fixed release, can let an attacker who holds a valid JWT bypass all but the first condition of a multi-condition jwt where filter used with the @authentication directive. The attacker can reach this remotely over the network with low-privilege login and no user interaction.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects npm packages
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
Impact
- Widely used
@neo4j/graphql has 38k weekly downloads.Source: npmjs.com
What to do
Upgrade to a fixed version: 7.6.7.
Workaround: Express multi-condition jwt where filters with an explicit AND array or with the inline operator syntax (for example roles_INCLUDES: "admin").
Timeline
- CVE published
- First seen by cve.now
Affected versions
From 7.0.0 · fixed in 7.6.7
Fixed in 7.6.7 (released Nov 5, 2026, 4 days before disclosure).
The latest release, 7.6.7, is not affected.
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-92683
Is CVE-2026-92683 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
Which versions are affected by CVE-2026-92683?
@neo4j/graphql (npm): from 7.0.0 before 7.6.7.Source: cve.now feed data
How do I fix CVE-2026-92683?
Upgrade @neo4j/graphql to version 7.6.7 or later. Until you can upgrade, express multi-condition JWT where filters with an explicit AND array or with the inline operator syntax, such as roles_INCLUDES: "admin".Source: cve.org