CVE-2025-71395GHSA-3633-G6MG-P6QQ
SurrealDB before 2.2.2 Memory Exhaustion via string::replace
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.2.2, 2.1.5, 2.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SurrealDB versions before 2.2.2 contain a memory exhaustion vulnerability in the string::replace function that fails to restrict resulting string length when using regex patterns. An authenticated attacker can craft a malicious query to exhaust server memory through unbounded string allocations, causing denial of service.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- surrealdb surrealdb
From 2.2.0 · fixed in 2.2.2
- surrealdb surrealdb
From 2.1.0 · fixed in 2.1.5
- surrealdb surrealdb
fixed in 2.0.5
- surrealdbcrates.io
From 2.2.0 · fixed in 2.2.2
- surrealdbcrates.io
From 2.1.0 · fixed in 2.1.5
- surrealdbcrates.io
fixed in 2.0.5