SurrealDB before 2.0.5, 2.1.x before 2.1.5, and 2.2.x before 2.2.2 allows authenticated users with OWNER or EDITOR permissions (at the root, namespace, or database level) to define custom database functions via DEFINE FUNCTION using nested FOR loops. Although a single loop's iteration count is constrained, nesting multiple loops (e.g., each with 1,000,000 iterations) is not, so an attacker can execute a function that consumes all server CPU time. Configured timeouts do not stop the execution, rendering the server unresponsive to other queries and connections until it is manually restarted.
CVE-2025-71397
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EPSS
- 20.8%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026SurrealDB before 2.2.2 CPU Exhaustion via nested FOR loops | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-cpu-exhaustion-via-nested-for-loopsCPU exhaustion via custom functions result in total DoS · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pxw4-94j3-v9pfVendor Advisories for CVE-2025-71397(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| surrealdb | — | 2.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:52 UTCEG score recompute
- 2026-07-20 17:52 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 16:05 UTCEG score recompute
- 2026-07-18 16:05 UTCGHSA enrichment
- 2026-07-18 13:40 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2025-71397?
When was CVE-2025-71397 disclosed?
Is CVE-2025-71397 actively exploited?
What is the CVSS score of CVE-2025-71397?
How do I remediate CVE-2025-71397?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71397
Is Your Infrastructure Affected by CVE-2025-71397?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.