CVE-2026-92682— @neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier
Quick assessment
Affected
Neo4j @neo4j/graphql
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
在 @neo4j/graphql 7.0.0 至 7.6.4（不含）版本中， 过滤器对关系和连接使用的“none”量词（即“无”或“都不满足”）在转换为 Cypher 查询时未被正确取反，导致其行为类似于“some”（即“至少一个满足”）。因此，例如“无相关被拒绝的用户与 JWT 主题匹配”这一规则，实际上会返回原本应被排除的记录，而排除原本应返回的记录。这意味着，一个本应被该规则拒绝的已认证用户，反而可以读取受保护的记录。 该问题也存在于突变（mutations）操作中，因此敏感数据可能被无权访问的用户创建和删除
Possible ATT&CK Techniques 1 AI
T1528 · Steal Application Access TokenAffected Version Matrix 1
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Neo4j | @neo4j/graphql | 7.0.0< 7.6.4 |
affected |
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-92682
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
@neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier
Source: CVE Program / CVE List V5
Vulnerability Description
In @neo4j/graphql versions from 7.0.0 up to but not including 7.6.4, the none quantifier in @authorization filters on relationships and connections is not negated when translated to Cypher, so it behaves like some. A rule such as "none of the related denied users matches the JWT subject" therefore returns exactly the records it was meant to exclude, and excludes those it was meant to return. An authenticated user whom such a rule is meant to deny can read the protected records. This is also the case for mutations, so the impact is that sensitive data could also be created and deleted by users that shouldn't have access according to the typedefs. Fixed in 7.6.4.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不正确
Source: CVE Program / CVE List V5
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Neo4j | @neo4j/graphql | 7.0.0 ~ 7.6.4 | - |
|
II. Public POCs for CVE-2026-92682
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-92682
请登录查看更多情报信息。
Patches & Fixes for CVE-2026-92682 (1)
Vendor Advisories for CVE-2026-92682 (1)
Vendor Pages for CVE-2026-92682 (1)
-
🔗 Release @neo4j/graphql@7.6.4 · neo4j/graphql · GitHub release-notes
IV. Related Vulnerabilities
Same vendor: Neo4j
-
CVE-2026-92681
@neo4j/graphql: schema-level and type-level @authentication -
CVE-2026-19869
Privilege Escalation via Dropped Field-Level @authentication -
CVE-2026-5423
Subscription Authentication Bypass via Unverified connection -
CVE-2026-14587
Unathenticated connection can hold Bolt channel open -
CVE-2026-1471
Caching of authentication context
Same weakness: CWE-863
-
CVE-2026-89072
MOVEit Transfer Authorization Flaw in Certificate Management -
CVE-2026-73126
Gitea private workflow badge token scope bypass -
CVE-2026-71184
Gitea fork workflow approval bypass through review events -
CVE-2026-70406
Gitea private comparison disclosure with public-only tokens -
CVE-2026-70400
Gitea private migration creation with public-only tokens
V. Comments for CVE-2026-92682
No comments yet