Quick answers
- Is CVE-2025-71396 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71396 being exploited in the wild.
- How severe is CVE-2025-71396?
- Medium severity, with a CVSS score of 4, published 18 July 2026.
- Which products and versions are affected?
- surrealdb (crates.io) SEMVER:introduced=2.2.0,fixed=2.2.2.
- Is there a fix for CVE-2025-71396?
- Yes. surrealdb (crates.io): upgrade to 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71396 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-71396?
- Check whether you run surrealdb (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- surrealdb (crates.io): upgrade to 2.2.2 or later
cargo update -p surrealdb
Technical details
SurrealDB versions prior to 2.0.5, 2.1.5, and 2.2.2 contain a resource exhaustion vulnerability (CWE-770) in the embedded JavaScript scripting engine. While the engine enforces memory and stack limits, it lacks a default execution-time timeout. An authenticated attacker can exploit this by submitting long-running or infinite-loop JavaScript functions if scripting is explicitly enabled (via --allow-scripting or --allow-all). This leads to CPU exhaustion and a Denial of Service (DoS) condition. The issue has been resolved by implementing a default timeout and a configurable SURREAL_SCRIPTING_MAX_TIME_LIMIT environment variable.
Affected products
- SurrealDB SurrealDB < 2.0.5, 2.1.x < 2.1.5, 2.2.x < 2.2.2
Identifiers
- CVE-2025-71396
- GHSA-3824-qmfq-2qv7
Timeline
- 2025-04-10: advisory: GitHub Security Advisory published
- 2026-07-18: disclosed: NVD publication date