CVE-2025-71391
mediumpriority · track · 26EPSS 0.006 · 46 %ileEUUSEPSS · scored 2026-10-28
SurrealDB versions before 2.2.2 contain an uncaught exception vulnerability in the net module that allows authenticated users to crash the database. Attackers can send crafted HTTP queries containing null bytes to the /sql endpoint, causing an unhandled exception that crashes the SurrealDB instance and any dependent applications.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.9–7.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (7)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-rq86-9m6r-cm3gSurrealDB has uncaught exception in Net module that leads to database crash2025-04-10ghsa · osvUS
A vulnerability was found where an attacker can crash the database via crafting a HTTP query that returns a null byte. The problem relies on an uncaught exception in the `net` module, where the result of the query will be converted to JSON before showing as the HTTP response to the user in the **/sql** endpoint. ### Impact This vulnerability allows any authenticated user to crash a SurrealDB instance by sending a crafted query with a null byte to the /sql endpoint. Where SurrealDB is used as an application backend, it is possible that an application user can crash the SurrealDB instance and thus the supported application through crafted inputs that exploit this attack vector. ### Patches A patch has been introduced that ensures the error is caught and converted as an error. - Versions 2.2.2, 2.1.5 and 2.0.5 and later are not affected by this isssue ### Workarounds Affected users who are unable to update may want to limit the ability of untrusted clients to run arbitrary queries in the affected versions of SurrealDB. To limit the impact of the denial of service, SurrealDB administrators may also want to ensure that the SurrealDB process is running so that it can be automatically re-started after a crash. Where SurrealDB is used as an application backend, ensure sanitisation of input at the application layer to prevent injection attacks. ### References https://github.com/surrealdb/surrealdb/pull/5647
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/surrealdb/surrealdb/releasesPatchcnnvd
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-rq86-9m6r-cm3gcnnvd
- https://www.vulncheck.com/advisories/surrealdb-before-denial-of-service-via-sql-endpointcnnvd
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-rq86-9m6r-cm3genisa_euvd
- https://www.vulncheck.com/advisories/surrealdb-before-denial-of-service-via-sql-endpointenisa_euvd
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-rq86-9m6r-cm3gVendor Advisorynvd
- https://www.vulncheck.com/advisories/surrealdb-before-denial-of-service-via-sql-endpointThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan