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… (CVE-2024-58362)
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).
AI Analysis
Technical Summary
SurrealDB before 1.5.5 and 2.0.0-beta before 2.0.0-beta.3 has a vulnerability in its RPC API signin and signup operations where arbitrary objects are accepted without proper recursive validation. When a SIGNIN or SIGNUP query is defined and the RPC API is exposed to untrusted users, an attacker can supply a bincode-serialized binary object containing a subquery. This subquery executes under a system user session with editor role privileges, enabling modification of non-IAM resources. The attacker cannot directly view query results or affect IAM resources, which require owner role privileges.
Potential Impact
An unauthenticated attacker can execute arbitrary subqueries within the database owner's SIGNIN/SIGNUP query context with editor role permissions. This enables the attacker to select, create, update, and delete non-IAM resources. However, the attacker cannot view query results directly or modify IAM resources, limiting the scope of impact to non-IAM data manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict exposure of the RPC API signin and signup operations to trusted users only. Avoid defining SIGNIN or SIGNUP queries that accept arbitrary objects from untrusted sources. Monitor vendor channels for updates and apply patches promptly once released.
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… (CVE-2024-58362)
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).
CVSS v4.0
Affected software
pkg:github/surrealdb/surrealdbRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
SurrealDB before 1.5.5 and 2.0.0-beta before 2.0.0-beta.3 has a vulnerability in its RPC API signin and signup operations where arbitrary objects are accepted without proper recursive validation. When a SIGNIN or SIGNUP query is defined and the RPC API is exposed to untrusted users, an attacker can supply a bincode-serialized binary object containing a subquery. This subquery executes under a system user session with editor role privileges, enabling modification of non-IAM resources. The attacker cannot directly view query results or affect IAM resources, which require owner role privileges.
Potential Impact
An unauthenticated attacker can execute arbitrary subqueries within the database owner's SIGNIN/SIGNUP query context with editor role permissions. This enables the attacker to select, create, update, and delete non-IAM resources. However, the attacker cannot view query results directly or modify IAM resources, limiting the scope of impact to non-IAM data manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict exposure of the RPC API signin and signup operations to trusted users only. Avoid defining SIGNIN or SIGNUP queries that accept arbitrary objects from untrusted sources. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xw2c-hrr9-4xwr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2024-58362"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a5ba17f44ab8fbf7c789e65
Added to database: 07/18/2026, 15:53:35 UTC
Last enriched: 07/18/2026, 16:23:19 UTC
Last updated: 07/18/2026, 20:39:26 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.