CVE-2026-109333 SurrealDB 3.0.0 before 3.3.0 Cross-Tenant Record Read via RETURN FETCH
High 7.1
Published
Updated
Check this codebase for CVE-2026-109333 and fix it if it is affected.
What it is: CVE-2026-109333 is a high-severity vulnerability in surrealdb, published on 12 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-109333 in the wild and no public exploit code.
Affected product: surrealdb. 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-109333/ (Markdown: https://insights.sbomify.com/CVE-2026-109333/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-109333?
CVE-2026-109333 is a high-severity vulnerability in surrealdb, published on 12 Oct 2026.
Official description
SurrealDB from 3.0.0 before 3.3.0 contains an authorization bypass vulnerability that allows authenticated record users to read records in other namespaces or databases by resolving record ids through FETCH. Attackers can switch to a foreign namespace/database and name a known record id in a RETURN … FETCH query to read another tenant's data when table PERMISSIONS allow reads.
Weakness: CWE-862
Which versions are affected by CVE-2026-109333?
How do I fix CVE-2026-109333?
No fix has been published for CVE-2026-109333 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-109333 being exploited?
There is no known exploitation of CVE-2026-109333 in the wild and no public exploit code.
Sources
Also known as GHSA-7r25-4gw2-w5j3.