SurrealDB before 2.2.2 with scripting enabled fails to properly enforce recursion limits when native functions contain embedded JavaScript that issues new queries. Authenticated attackers can bypass the recursion limit by chaining native and JavaScript function calls to trigger infinite recursion and exhaust server memory.
CVE-2025-71393
This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.0
- EG Score
- 6.0(low)
- EPSS
- 16.3%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026SurrealDB before 2.2.2 Memory Exhaustion via Nested Functions | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-memory-exhaustion-via-nested-functionsMemory exhaustion via nested functions and scripts · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-m7rc-8w7m-r9qrVendor Advisories for CVE-2025-71393(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 9× in last 7d / 9× 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:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 16:06 UTCEG score recompute
- 2026-07-18 16:06 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-71393?
When was CVE-2025-71393 disclosed?
Is CVE-2025-71393 actively exploited?
What is the CVSS score of CVE-2025-71393?
How do I remediate CVE-2025-71393?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71393
Is Your Infrastructure Affected by CVE-2025-71393?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.