CVE-2024-58362

SurrealDB before 1.5.5 Query Injection via RPC API

Published Jul 18, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
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).

Analysis

AI-generated

Technical impact

SurrealDB versions before 1.5.5 (and 2.0.0-beta before 2.0.0-beta.3) allow an attacker to send an arbitrary bincode‑serialized object as credentials in RPC sign‑in or sign‑up operations without proper validation of nested fields. The injected object can contain a subquery that is executed within the database owner's SIGNIN or SIGNUP query under a system session with the editor role, granting the attacker the ability to SELECT, CREATE, UPDATE, and DELETE non‑IAM resources. The attacker cannot view query results directly or affect IAM resources, but can still compromise data integrity and confidentiality for non‑IAM data.

Affected Systems

The vulnerability affects the SurrealDB product, specifically all releases prior to version 1.5.5 and prior to 2.0.0‑beta.3. These versions are used in environments where the RPC API is exposed to untrusted users, allowing the subquery injection described above.

Risk and Exploitability

With a CVSS score of 8.7, the vulnerability is considered high severity. The EPSS score of less than 1% indicates that the likelihood of exploitation remains low at present, and the vulnerability is not included in the CISA KEV catalog. The attack vector is inferred to be remote, as the exploit requires access to the exposed RPC API and does not require authentication. A successful exploit would allow an unauthenticated attacker to modify or retrieve sensitive non‑IAM data, potentially leading to significant operational damage.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade SurrealDB to version 1.5.5 or newer; if using the beta line, upgrade to 2..0‑beta.3 or later. This patch validates the RPC credentials object recursively and removes the injection path.
  • Configure the RPC API so that only trusted, authenticated users can access it, e.g., by enabling network‑level firewall rules or internal‑only routing for the RPC endpoint. This limits the exposure window for the vulnerability even if a patch is not immediately available.
  • Review and tighten application logs to detect anomalous subquery payloads or unusual database activity, and monitor for unauthorized data access patterns.

Generated by OpenCVE AI on July 30, 2026 at 23:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-xw2c-hrr9-4xwr Duplicate Advisory: Untrusted Query Object Evaluation in RPC API
History
Type Values Removed Values Added
CPEs cpe:2.3:a:surrealdb:surrealdb:2.0.0:beta1:*:*:*:*:*:*
cpe:2.3:a:surrealdb:surrealdb:2.0.0:beta2:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Surrealdb
Surrealdb surrealdb
Vendors & Products Surrealdb
Surrealdb surrealdb
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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).
Title SurrealDB before 1.5.5 Query Injection via RPC API
Weaknesses CWE-75
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-75

    Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Jul 28, 2026, 1:47 AM
Reserved
Jul 18, 2026, 12:40 PM
Status
Analyzed
Published
Jul 18, 2026, 2:17 PM
Modified
Oct 27, 2026, 6:10 PM