Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63735 high CVSS 8.1

Vulnerability in surrealdb (CVE-2026-63735)

Summary

Vulnerability in surrealdb (CVE-2026-63735). Confidential information can be exposed externally. Exploitable via PERMISSIONS. Mitigation: upgrade to 3.2.0 or later.

Original description

The description as published by the source.

An authenticated user scoped to one namespace/database could invoke a custom API (DEFINE API) belonging to a different namespace/database, reaching another tenant's endpoint.

The route /api/{namespace}/{database}/{endpoint} took the namespace and database from the URL and applied them to the caller's session before the endpoint was looked up or run, without checking that the caller's authenticated scope covered them. Because a custom API handler runs with permissions disabled (definer's rights), the endpoint's own PERMISSIONS clause was the only gate — open to everyone for a PERMISSIONS FULL endpoint. The api::invoke() function was affected the same way, resolving against the session's selected namespace/database (settable via the surreal-ns / surreal-db headers or USE).

Impact

What an attacker can do:

  • With valid credentials for any one namespace/database (a VIEWER is enough), invoke a custom API in another namespace/database by naming the victim scope in the URL.
  • Read data that endpoint returns — including from PERMISSIONS NONE tables, since the handler runs with permissions disabled — or trigger any writes and side effects it performs.

What it can't do:

  • Reach a scope without valid credentials for some namespace/database on the instance; this is not an unauthenticated bypass.
  • Affect single-tenant deployments, or any deployment where callers already hold instance-wide (root) scope.

Patches

The namespace/database is now valid…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-63735 has been found in surrealdb.
Attackers can target a specific entry point like PERMISSIONS over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade surrealdb to 3.2.0 or later.
If unsure, ask your IT team or search "surrealdb CVE-2026-63735" on the vendor's site.

CVE-2026-63735 (surrealdb) — CWE-639 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PERMISSIONS / USE / VIEWER
Patched: 3.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in surrealdb. Attackers reach the vulnerable code path via PERMISSIONS.

📍 Affected scope

Check the vendor advisory for the affected versions of surrealdb. Attack surface: PERMISSIONS / USE / VIEWER.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.2.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'surrealdb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'surrealdb' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で surrealdb を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade surrealdb to 3.2.0

    ステージング環境で 3.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust surrealdb
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details