Quick answers
- Is CVE-2024-58361 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-58361 being exploited in the wild.
- How severe is CVE-2024-58361?
- Medium severity, with a CVSS score of 6.5, published 18 July 2026.
- Which products and versions are affected?
- surrealdb (crates.io) SEMVER:introduced=2.0.0,fixed=2.0.4; surrealdb-core (crates.io) SEMVER:introduced=2.0.0,fixed=2.0.4; Surrealdb-Core >= 2.0.0, < 2.0.4.
- Is there a fix for CVE-2024-58361?
- Yes. surrealdb (crates.io): upgrade to 2.0.4 or later; surrealdb-core (crates.io): upgrade to 2.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-58361 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2024-58361?
- Check whether you run surrealdb (crates.io), surrealdb-core (crates.io) or Surrealdb-Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- surrealdb (crates.io): upgrade to 2.0.4 or later
cargo update -p surrealdb - surrealdb-core (crates.io): upgrade to 2.0.4 or later
cargo update -p surrealdb-core
Technical details
An uncaught exception (CWE-248) exists in the SurrealDB parser's error rendering logic. When an authorized client submits a query that attempts to convert an empty string into specific types—such as record, duration, or datetime—the parser fails. The subsequent error rendering code fails to handle this state correctly and triggers a Rust 'panic'. Because the exception is not caught, the entire database process terminates. This vulnerability is reachable over the network by any user with privileges to execute queries. The issue is resolved in version 2.0.4.
Affected products
- SurrealDB SurrealDB >= 2.0.0, < 2.0.4
- SurrealDB surrealdb-core >= 2.0.0, < 2.0.4
Identifiers
- CVE-2024-58361
- GHSA-qjrv-v6qp-x99x
Timeline
- 2024-10-08: advisory: Original GitHub Security Advisory published
- 2026-07-18: disclosed: CVE published to NVD
- 2024-10-08: patched: Version 2.0.4 released to address the issue