Skip to main content
Menu
CVEs

SurrealDB authorization bypass in implicit table creation

Affects SurrealDB 3.0.0 before 4.0.0 in databases that are not STRICT. CVSS scores it 5.3 (medium); no vendor rating is given. Fixed in 4.0.0.

CVE-2026-134298Published November 21, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0
Who is exposed
Specific setups only

Summary

Written by a model

SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass that allows users with the read-only VIEWER role to modify database schema, because CREATE on a nonexistent table implicitly defines it without the DEFINE TABLE permission check applied to explicit definitions. Authenticated VIEWER users can issue CREATE statements in non-STRICT databases to add arbitrary empty SCHEMALESS tables, cluttering schemas or colliding with application table names.

Who should check

Teams running SurrealDB 3.x (crates.io surrealdb crate) with VIEWER-role users, especially service or backup/reporting accounts, on non-STRICT databases.

“in a database that is not STRICT”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Database is not STRICT (non-STRICT database). Affected SurrealDB versions are 3.0.0 before 4.0.0.
  2. Upgrade to a fixed version: 4.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134298 (SurrealDB 3.0.0 before 4.0.0 VIEWER Role Authorization Bypass via Implicit Table Creation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134298 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 3.0.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- Database is not STRICT (non-STRICT database). (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-m887-2246-mgw3)
- Affected SurrealDB versions are 3.0.0 before 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-viewer-role-authorization-bypass-via-implicit-table-creation)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134298 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134298 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-m887-2246-mgw3
- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-viewer-role-authorization-bypass-via-implicit-table-creation
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134298
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134298"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects crates.io packages
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 30 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · surrealdb/surrealdb · Advisory GHSA-m887-2246-mgw3
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134298
RecordNVD · CVE-2026-134298
Other links 1
Linkvulncheck.com · advisories/surrealdb-3.0.0-before-4.0.0-viewer-role-authorization-bypass-via-implicit-table-creation

Questions about CVE-2026-134298

Is CVE-2026-134298 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

What does this mean?

A user with the read-only VIEWER role can add arbitrary empty SCHEMALESS tables to non-STRICT databases, which changes the database schema. The role is meant to be read-only, so this is an authorization bypass.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134298?

surrealdb (crates.io): from 3.0.0 before 4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are SurrealDB 3.0.0 before 4.0.0, and only in databases that are not STRICT. To check, look at the SurrealDB version in use and whether the database is set to STRICT.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134298?

Upgrade SurrealDB to 4.0.0 or later, which is the listed fixed version.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.