How severe is CVE-2024-58361?

No CVSS score has been assigned to CVE-2024-58361 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-58361?

CVE-2024-58361 affects the following packages: surrealdb (crates.io), surrealdb-core (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2024-58361?

Update surrealdb to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-58361 is resolved across your whole dependency graph.

How do I detect CVE-2024-58361 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for surrealdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-58361 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2024-58361 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-58361 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-58361?

CVE-2024-58361 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-58361?

CVE-2024-58361 is classified as CWE-248 (CWE-248). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-58361 published, and has it been updated?

CVE-2024-58361 was published on July 18, 2026 and was last updated on October 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

CVE-2024-58361 — surrealdb

Fix: surrealdb/surrealdb#4923

CVE-2024-58361 is a CWE-248 vulnerability in surrealdb. A fix is available for surrealdb — see the affected versions and patch details below.

SurrealDB before 2.0.4 Denial of Service via Parser Exception

Also known asGHSA-qjrv-v6qp-x99x

Published

Jul 18, 2026

Updated

Oct 29, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-58361.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🦀surrealdb🦀surrealdb-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A client that is authorized to run queries in a SurrealDB server would be able to execute a malformed query which would fail to parse when converting an empty string and cause a panic in the error rendering code. This would crash the server, leading to denial of service.

Patches

Version 2.0.4 and later are not affected by this issue.

Workarounds

Affected users who are unable to update may want to limit the ability of untrusted clients to run arbitrary SurrealQL 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`surrealdb`	≥ 2.0.0&&< 2.0.4	2.0.4`cargo update -p surrealdb --precise 2.0.4`
🦀crates.io	`surrealdb-core`	≥ 2.0.0&&< 2.0.4	2.0.4`cargo update -p surrealdb-core --precise 2.0.4`

Affected Products

1 product · 1 configurations

Application

surrealdbsurrealdb

≥ 2.0.0 && < 2.0.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for surrealdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update surrealdb to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-58361 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

The error rendering code from the parser would panic when handling failed parsing of queries where the error occurred when converting an empty string to a SurrealDB value. This would be the case when casting an empty string to a `record`, `duration` or `datetime`, as well as potentially when parsing an empty string to JSON or providing an empty string to the `type::field` and `type::fields` functions. ### Impact A client that is authorized to run queries in a SurrealDB server would be able to execute a malformed query which would fail to parse when converting an empty string and cause a pani

O3 Security · Impact-Aware SCA

Is CVE-2024-58361 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works