Vulnerability in surrealdb (CVE-2026-63760)
Summary
Vulnerability in surrealdb (CVE-2026-63760). Risk of unauthorized operations or information disclosure. Exploitable via parse_value. Mitigation: upgrade to 3.1.0 or later.
Original description
The description as published by the source.
The SurrealDB value and JSON parser did not enforce the configured recursion depth limit when parsing nested {, [, or ( tokens. The expression parser already enforced the limit for these tokens; the value/JSON parser omitted it. An unauthenticated attacker could send a deeply nested JSON payload to the WebSocket /rpc endpoint and exhaust server memory, crashing the process.
This is an incomplete fix for GHSA-6r8p-hpg7-825g, which addressed the same class of bug in the expression parser but did not cover the value/JSON parser code path.
Impact
An unauthenticated remote attacker can crash a SurrealDB server with a single WebSocket message. No credentials or query execution privileges are required.
Patches
A patch enforces the configured recursion depth limit in parse_value and parse_json, bringing them in line with the rest of the parser.
- Versions 3.1.0 and later are not affected by this issue.
Workarounds
Restrict network access to the WebSocket /rpc endpoint to trusted clients.
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-63760 has been found in surrealdb.
Attackers can target a specific entry point like parse_value over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade surrealdb to 3.1.0 or later.
If unsure, ask your IT team or search "surrealdb CVE-2026-63760" on the vendor's site.
CVE-2026-63760 (surrealdb) — CWE-674 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: parse_value / parse_json
Patched: 3.1.0 — apply immediately
Workaround: Restrict network access to the WebSocket /rpc endpoint to trusted clients.
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-674) exists in surrealdb. Attackers reach the vulnerable code path via parse_value without authentication.
Check the vendor advisory for the affected versions of surrealdb. Attack surface: parse_value / parse_json.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 3.1.0.
Workaround: Restrict network access to the WebSocket /rpc endpoint to trusted clients.
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
Restrict network access to the WebSocket `/rpc` endpoint to trusted clients.パッチが適用されるまでの応急処置として、Restrict network access to the WebSocket
/rpcendpoint to trusted clients. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade surrealdb to 3.1.0ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web vulncheck.com
- web github.com
- web github.com
- web github.com