# CVE-2026-10130: QueryWeaver Authentication Bypass via Email Signup Token Issuance for Existing Accounts

> Unauthenticated attackers can hijack existing accounts by triggering signup token issuance for known email addresses, bypassing authentication checks.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-hxxv-mxpg-3h6j

## What is CVE-2026-10130?

CVE-2026-10130 is a high-severity authentication bypass vulnerability in FalkorDB QueryWeaver, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QueryWeaver contains an authentication bypass vulnerability that allows unauthenticated attackers to obtain valid session tokens for existing accounts by submitting a signup request with a known victim email address. The signup route unconditionally creates and links a new token to the matching Identity via a Cypher MERGE operation before checking whether the email belongs to an existing account, causing the server to return a valid authenticated session token for the victim's identity without requiring any prior credentials or user interaction.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-10130 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10130 is a high-severity authentication bypass vulnerability in FalkorDB QueryWeaver, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10130 in the wild and no public exploit code.

Affected product: FalkorDB QueryWeaver. 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-10130/ (Markdown: https://insights.sbomify.com/CVE-2026-10130/index.md)
```

## Sources

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

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