# CVE-2026-92682: @neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier

> Authenticated users can bypass authorization filters to read, create, or delete protected records due to inverted logic in relationship filters.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-h873-p2wr-fjx6

## What is CVE-2026-92682?

CVE-2026-92682 is a high-severity missing authorization vulnerability in @neo4j/graphql, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-92682?


## How do I fix CVE-2026-92682?

No fix has been published for CVE-2026-92682 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92682 being exploited?

There is no known exploitation of CVE-2026-92682 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92682 and fix it if it is affected.

What it is: CVE-2026-92682 is a high-severity missing authorization vulnerability in @neo4j/graphql, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92682 in the wild and no public exploit code.

Affected product: @neo4j/graphql. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92682/ (Markdown: https://insights.sbomify.com/CVE-2026-92682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92682
- OSV: https://osv.dev/vulnerability/CVE-2026-92682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92682/
Summaries are generated and may contain mistakes; the official description above is the record.