Cyber Resilience

CVE-2024-58362

Surrealdb ≤ 1.5.5

Public PoC
Published
18 July 2026
Modified
12 August 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0037 30th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2024-58362 is a high-severity Special Element Injection (CWE-75) vulnerability in Surrealdb Surrealdb. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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).

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-63744Same product: Surrealdb Surrealdb
CVE-2026-63745Same product: Surrealdb Surrealdb
CVE-2026-63736Same product: Surrealdb Surrealdb
CVE-2026-63739Same product: Surrealdb Surrealdb
CVE-2026-63735Same product: Surrealdb Surrealdb
CVE-2026-63743Same product: Surrealdb Surrealdb
CVE-2026-63763Same product: Surrealdb Surrealdb
CVE-2026-63757Same product: Surrealdb Surrealdb
CVE-2026-63758Same product: Surrealdb Surrealdb
CVE-2026-63741Same product: Surrealdb Surrealdb

Affected Assets

surrealdb
surrealdb
2.0.0 · ≤ 1.5.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly stops special-element injection by rejecting or sanitizing untrusted data before it reaches a different control plane.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input sanitization to block special-element injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing catches injection vulnerabilities but does not itself implement the sanitization fix.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

prevents

Secure development life cycle mandates input validation and sanitization practices that directly prevent special-element injection.

prevents

Application security requirements explicitly call for controls against injection flaws including special-element handling.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe the actual sanitization logic.

prevents

Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.

References