SurrealDB before 1.5.5 (and 2.0.0-beta before 2.0.0-beta.3) accepts an arbitrary object in the signin and signup operations of the RPC API without recursively validating it for non-computed values. When a record access method defines a SIGNIN or SIGNUP query and the RPC API is exposed to untrusted users, an unauthenticated attacker can encode a binary object containing a subquery using the bincode serialization format and supply it in place of credentials. The subquery is then executed within the database owner's SIGNIN/SIGNUP query under a system user session with the editor role, allowing the attacker to select, create, update, and delete non-IAM resources (though not view the query results directly, and not affect IAM resources, which require the owner role).
CVE-2024-58362
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-18. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- 29.2%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026SurrealDB before 1.5.5 Query Injection via RPC API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-query-injection-via-rpc-apiUntrusted Query Object Evaluation in RPC API · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-64f8-pjgr-9wmrVendor Advisories for CVE-2024-58362(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 | — | 1.5.5 | — |
| surrealdb-core | — | 1.5.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× 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-22 14:07 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 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:40 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2024-58362?
When was CVE-2024-58362 disclosed?
Is CVE-2024-58362 actively exploited?
What is the CVSS score of CVE-2024-58362?
How do I remediate CVE-2024-58362?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-58362
Is Your Infrastructure Affected by CVE-2024-58362?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.