Answer in brief
CVE-2025-71392 records a Critical severity (CVSS 9.4) vulnerability in SurrealDB before 2.2.2 SurrealQL Injection via export. The current sources do not mark it as known exploited. The current feed maps surrealdb (crates.io), surrealdb (crates.io), surrealdb (crates.io), surrealdb/surrealdb (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps surrealdb (crates.io), surrealdb (crates.io), surrealdb (crates.io), surrealdb/surrealdb (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| surrealdbcrates.io | >=2.2.0 <2.2.2 | 2.2.2 |
| surrealdbcrates.io | >=2.1.0 <2.1.5 | 2.1.5 |
| surrealdbcrates.io | >=0 <2.0.5 | 2.0.5 |
| surrealdb/surrealdbgeneric | >=0 <2.2.2 | 2.2.2 |
| surrealdb/surrealdbgeneric | >=0 <2.1.5 | 2.1.5 |
| surrealdb/surrealdbgeneric | >=0 <2.0.5 | 2.0.5 |
| surrealdbrust | >=2.2.0,<2.2.2 | 2.2.2 |
| surrealdbrust | >=2.1.0,<2.1.5 | 2.1.5 |
| surrealdbrust | <2.0.5 | 2.0.5 |
Published upstream
Jul 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.