Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-71394 medium CVSS 4.3

Path Traversal in surrealdb (CVE-2025-71394)

Summary

Path traversal in surrealdb (CVE-2025-71394). Risk of unauthorized operations or information disclosure. Exploitable via SURREAL_FILE_ALLOWLIST. Mitigation: upgrade to 2.1.5 or later.

Original description

The description as published by the source.

An authenticated system user at the root, namespace, or database levels can use the DEFINE ANALYZER statement to point to arbitrary file locations on the file system, and should the file be tab separated with two columns, the analyzer can be leveraged to exfiltrate the content.

This issue was discovered and patched during an code audit and penetration test of SurrealDB by cure53, the severity defined within cure53's preliminary finding is Low, matched by our CVSS v4 assessment.

Impact

Limited to unauthorised access to 2 column TSV files on the file system

Patches

A patch has been created that introduces a new environment variable, SURREAL_FILE_ALLOWLIST , which contains a list of allowed file paths. When a mapping file is processed, the mapper checks if the file’s path is within one of the allowed paths.

  • Versions 2.1.5, 2.2.2 and later are not affected by this issue.

Workarounds

Users unable to update may want to limit those with root, namespace, or database level users to trusted parties only.

References

SurrealQL Documentation - DEFINE ANALYZER
#5600

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-71394 has been found in surrealdb.
Attackers can target a specific entry point like SURREAL_FILE_ALLOWLIST over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade surrealdb to 2.1.5 or later.
If unsure, ask your IT team or search "surrealdb CVE-2025-71394" on the vendor's site.

CVE-2025-71394 (surrealdb) — CWE-22 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SURREAL_FILE_ALLOWLIST
Patched: 2.1.5 — apply immediately
Workaround: Users unable to update may want to limit those with root, namespace, or database level users to trusted parties only.
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

Path traversal (CWE-22) exists in surrealdb. Attackers reach the vulnerable code path via SURREAL_FILE_ALLOWLIST.

📍 Affected scope

Check the vendor advisory for the affected versions of surrealdb. Attack surface: SURREAL_FILE_ALLOWLIST.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.1.5.

🛡️ Workaround

Workaround: Users unable to update may want to limit those with root, namespace, or database level users to trusted parties only.

🔍 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 temporary workaround mitigate 
    Users unable to update may want to limit those with root, namespace, or database level users to trusted parties only.

    パッチが適用されるまでの応急処置として、Users unable to update may want to limit those with root, namespace, or database level users to trusted parties only. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade surrealdb to 2.1.5

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

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

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

Affected packages

crates.io surrealdb
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.1.5"}]}]

References

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