SurrealDB versions before 2.1.0 contain a denial of service vulnerability in the sorting mechanism when using ORDER BY rand() clause. Authorized clients can execute queries with ORDER BY rand() to trigger a panic in the sorting function, crashing the server.
CVE-2024-58359
MEDIUMPre-NVD 6.56.5—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-18. a secondary CVSS source baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 22.9%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026Patch available. Sources: github.
generic
SurrealDB before 2.1.0 Denial of Service via rand() Sorting | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-denial-of-service-via-rand-sortinggithub Patch Available
Uncaught Exception Sorting Tables by Random Order · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-m52v-24p8-654fVendor Advisories for CVE-2024-58359(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
crates.io(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| surrealdb | — | 2.1.0 | — |
| surrealdb-core | — | 2.1.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 02:45 UTCEG score recompute
- 2026-07-23 00:00 UTCEG score recompute
- 2026-07-23 00:00 UTCGHSA enrichment
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-20 17:52 UTCEG score recompute
- 2026-07-20 17:52 UTCGHSA enrichment
- 2026-07-20 17:07 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 16:07 UTCEG score recompute
- 2026-07-18 16:07 UTCGHSA enrichment
- 2026-07-18 13:41 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2024-58359?
CVE-2024-58359 is a medium vulnerability published on July 18, 2026. SurrealDB versions before 2.1.0 contain a denial of service vulnerability in the sorting mechanism when using ORDER BY rand() clause. Authorized clients can execute queries with ORDER BY rand() to trigger a panic in the sorting function, crashing the server.
When was CVE-2024-58359 disclosed?
CVE-2024-58359 was first published in the National Vulnerability Database on July 18, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-58359 actively exploited?
CVE-2024-58359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-58359?
CVE-2024-58359 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-58359?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-58359, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-58359
Is Your Infrastructure Affected by CVE-2024-58359?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.