SSRF (Server-Side Request Forgery) in surrealdb (CVE-2025-71398)
Summary
SSRF in surrealdb (CVE-2025-71398). Confidential information can be exposed externally. Exploitable via SURREAL_CAPS_ALLOW_NET. Mitigation: upgrade to 2.0.5 or later.
Original description
The description as published by the source.
SurrealDB offers http functions that can access external network endpoints. A typical, albeit not recommended configuration would be to start SurrealDB with all network connections allowed with the exception of a deny list. For example, surreal start --allow-net --deny-net 10.0.0.0/8 will allow all network connections except to the 10.0.0.0/8 block.
An authenticated user of SurrealDB can use redirects to bypass this restriction. For example by hosting a server on the public internet which redirects to the IP addresses blocked by the administrator of the SurrealDB server via HTTP 301 or 307 response codes.
When sending SurrealDB statements containing the http::* functions to the attacker controlled host, the SurrealDB server will follow the redirects to the blocked IP address. Because the statements also return the responses to the attacker, this issue constitutes a full SSRF vulnerability.
This issue was discovered and patched during an code audit and penetration test of SurrealDB by cure53, the severity as defined within cure53's preliminary finding is Medium, matched by our CVSS v4 assessment.
Impact
The impact of this vulnerability is circumvention of the --deny-net capability and resulting impact on systems external to SurrealDB. The ultimate impact is dependent on the deployment scenario.
For example, if the SurrealDB serve…
Source: NIST National Vulnerability Database 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-2025-71398 has been found in surrealdb.
Attackers can target a specific entry point like SURREAL_CAPS_ALLOW_NET over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade surrealdb to 2.0.5 or later.
If unsure, ask your IT team or search "surrealdb CVE-2025-71398" on the vendor's site.
CVE-2025-71398 (surrealdb) — CWE-918 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SURREAL_CAPS_ALLOW_NET / SURREAL_CAPS_DENY_NET
Patched: 2.0.5 — 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.
SSRF (CWE-918) exists in surrealdb. Attackers reach the vulnerable code path via SURREAL_CAPS_ALLOW_NET.
Check the vendor advisory for the affected versions of surrealdb. Attack surface: SURREAL_CAPS_ALLOW_NET / SURREAL_CAPS_DENY_NET.
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.
Update to 2.0.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade surrealdb to 2.0.5ステージング環境で 2.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com