Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-71395 medium CVSS 6.5

Vulnerability in surrealdb (CVE-2025-71395)

Summary

Vulnerability in surrealdb (CVE-2025-71395). Risk of unauthorized operations or information disclosure. Exploitable via SURREAL_GENERATION_ALLOCATION_LIMIT. Mitigation: upgrade to 2.0.5 or later.

Original description

The description as published by the source.

An authenticated user can craft a query using the string::replace function that uses a Regex to perform a string replacement. As there is a failure to restrict the resulting string length, this enables an attacker to send a string::replace function to the SurrealDB server exhausting all the memory of the server due to string allocations. This eventually results in a Denial-of-Service situation for the SurrealDB server.

This issue was discovered and patched during an code audit and penetration test of SurrealDB by cure53. Using CVSSv4 definitions, the severity is High.

Impact

An authenticated user can crash the SurrealDB instance through memory exhaustion

Patches

A patch has been created that enforces a limit on string length SURREAL_GENERATION_ALLOCATION_LIMIT

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

Workarounds

Affected users who are unable to update may want to limit the ability of untrusted clients to run the string::replace function in the affected versions of SurrealDB using the --deny-functions flag described within Capabilities or the equivalent SURREAL_CAPS_DENY_FUNC environment variable.

References

SurrealQL Documentation - DB Functions (string::replace)
[SurrealDB Documentation - Capabilities](https://surrealdb.com/docs/surrealdb/security/capabiliti…

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

CVE-2025-71395 (surrealdb) — CWE-789 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SURREAL_GENERATION_ALLOCATION_LIMIT / SURREAL_CAPS_DENY_FUNC
Patched: 2.0.5 — apply immediately
Workaround: Affected users who are unable to update may want to limit the ability of untrusted clients to run the string::replace function in the affected versions of SurrealDB using the --deny-functions flag described within [Capabilities](https://surrealdb
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-789) exists in surrealdb. Attackers reach the vulnerable code path via SURREAL_GENERATION_ALLOCATION_LIMIT.

📍 Affected scope

Check the vendor advisory for the affected versions of surrealdb. Attack surface: SURREAL_GENERATION_ALLOCATION_LIMIT / SURREAL_CAPS_DENY_FUNC.

🔥 Severity

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

🔧 How to fix

Update to 2.0.5.

🛡️ Workaround

Workaround: Affected users who are unable to update may want to limit the ability of untrusted clients to run the string::replace function in the affected versions of SurrealDB using the --deny-functions flag described within [Capabilities](https://surrealdb

🔍 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 
    Affected users who are unable to update may want to limit the ability of untrusted clients to run the `string::replace` function in the affected versions of SurrealDB using the `--deny-functions` flag described within [Capabilities](https://surrealdb

    パッチが適用されるまでの応急処置として、Affected users who are unable to update may want to limit the ability of untrusted clients to run the string::replace function in the affected versions of SurrealDB using the --deny-functions flag described within [Capabilities](https://surrealdb を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade surrealdb to 2.0.5

    ステージング環境で 2.0.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.0.5"}]}]

References

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