Vulnerability in surrealdb (CVE-2026-63763)
Summary
Vulnerability in surrealdb (CVE-2026-63763). Successful exploitation can lead to full system takeover. Exploitable via futures. Mitigation: upgrade to 3.0.0-beta.3 or later.
Original description
The description as published by the source.
SurrealDB before 2.5.0 and before 3.0.0-beta.3 contains a confused deputy privilege escalation vulnerability. Unprivileged users (e.g., those with the database editor role) can create or modify fields containing futures, functions, or closures. Because these are executed in the context of the invoking/querying user rather than their creator, an attacker can plant malicious logic that executes with a higher-privileged user's permissions when that user reads or writes the affected record. This can lead to full privilege escalation, including creation of a root owner and server takeover.
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-63763 has been found in surrealdb.
Attackers can target a specific entry point like futures over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade surrealdb to 3.0.0-beta.3 or later.
If unsure, ask your IT team or search "surrealdb CVE-2026-63763" on the vendor's site.
CVE-2026-63763 (surrealdb) — CWE-441 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: futures / Futures / closures / computed
Patched: 3.0.0-beta.3 — apply immediately
Workaround: Users unable to patch are advised to evaluate their use of the database to identify where low privileged users are able to define logic subsequently executed by privileged users, such as apis, functions, futures fields and events, and recommended to
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.
A vulnerability (CWE-441) exists in surrealdb. Attackers reach the vulnerable code path via futures.
Check the vendor advisory for the affected versions of surrealdb. Attack surface: futures / Futures / closures / computed.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 3.0.0-beta.3.
Workaround: Users unable to patch are advised to evaluate their use of the database to identify where low privileged users are able to define logic subsequently executed by privileged users, such as apis, functions, futures fields and events, and recommended to
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
-
1Identify exposure identify
grep -r 'surrealdb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
surrealdbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Users unable to patch are advised to evaluate their use of the database to identify where low privileged users are able to define logic subsequently executed by privileged users, such as apis, functions, futures fields and events, and recommended toパッチが適用されるまでの応急処置として、Users unable to patch are advised to evaluate their use of the database to identify where low privileged users are able to define logic subsequently executed by privileged users, such as apis, functions, futures fields and events, and recommended to を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade surrealdb to 3.0.0-beta.3ステージング環境で 3.0.0-beta.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com