SurrealDB before 2.0.5, 2.1.x before 2.1.5, and 2.2.x before 2.2.2 fails to properly escape table and field names in the command-line export command. An authenticated System User with OWNER or EDITOR roles can create tables or fields with malicious names containing SurrealQL. When a higher-privileged user subsequently imports the exported backup, the injected SurrealQL executes, enabling privilege escalation and root-level takeover of the SurrealDB instance. Applications that let users define custom tables or fields are also exposed to a universal second-order SurrealQL injection even when query parameters are sanitized.
CVE-2025-71392
This critical-severity CVE scores 9.4 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).
- 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
- 9.4
- EG Score
- 9.4(low)
- EPSS
- —
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 18, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026SurrealDB before 2.2.2 SurrealQL Injection via export | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-surrealql-injection-via-exportServer-takeover via SurrealQL injection on backup import · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-ccj3-5p93-8p42Vendor Advisories for CVE-2025-71392(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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-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)
Same CWE
10 shownCWE-77
- CVE-2016-15057EG 9.9CRITICAL
- CVE-2014-5470EG 9.8EPSS 95%CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8MEDIUM
- CVE-2017-20156NVD 5.5EG 9.8MEDIUM
- CVE-2016-20017EG 9.8 KEVEPSS 99%CRITICAL
- CVE-2016-4991EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2014-4982EG 9.8EPSS 91%CRITICAL
Frequently asked(4)
What is CVE-2025-71392?
When was CVE-2025-71392 disclosed?
What is the CVSS score of CVE-2025-71392?
How do I remediate CVE-2025-71392?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-71392
Is Your Infrastructure Affected by CVE-2025-71392?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.