SurrealDB versions before 1.5.4 have an authentication validation flaw when a scoped user switches databases using the USE clause or use method. (CVE-2024-58363)
SurrealDB versions before 1.5.4 have an authentication validation flaw when a scoped user switches databases using the USE clause or use method. This flaw allows an authenticated user to impersonate another user in a different database if a user record with the same identifier exists, potentially enabling unauthorized actions if permissions rely solely on the $auth parameter.
AI Analysis
Technical Summary
The vulnerability in SurrealDB prior to version 1.5.4 involves improper validation of authentication when a scoped user switches databases via the USE clause or use method. An attacker with an authenticated session can exploit this by impersonating an unrelated user in another database if that database contains a user record with an identical identifier. This can lead to unauthorized actions if the system's permission checks depend exclusively on the $auth parameter, effectively bypassing intended access controls.
Potential Impact
An attacker with an authenticated session can impersonate another user in a different database, potentially performing unauthorized actions if the application relies solely on the $auth parameter for permission enforcement. This could lead to privilege escalation or unauthorized data access within the affected SurrealDB instances.
Mitigation Recommendations
A fix is available in SurrealDB version 1.5.4. Users should upgrade to version 1.5.4 or later to address this authentication validation issue. No other mitigations are specified.
SurrealDB versions before 1.5.4 have an authentication validation flaw when a scoped user switches databases using the USE clause or use method. (CVE-2024-58363)
Description
SurrealDB versions before 1.5.4 have an authentication validation flaw when a scoped user switches databases using the USE clause or use method. This flaw allows an authenticated user to impersonate another user in a different database if a user record with the same identifier exists, potentially enabling unauthorized actions if permissions rely solely on the $auth parameter.
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
The vulnerability in SurrealDB prior to version 1.5.4 involves improper validation of authentication when a scoped user switches databases via the USE clause or use method. An attacker with an authenticated session can exploit this by impersonating an unrelated user in another database if that database contains a user record with an identical identifier. This can lead to unauthorized actions if the system's permission checks depend exclusively on the $auth parameter, effectively bypassing intended access controls.
Potential Impact
An attacker with an authenticated session can impersonate another user in a different database, potentially performing unauthorized actions if the application relies solely on the $auth parameter for permission enforcement. This could lead to privilege escalation or unauthorized data access within the affected SurrealDB instances.
Mitigation Recommendations
A fix is available in SurrealDB version 1.5.4. Users should upgrade to version 1.5.4 or later to address this authentication validation issue. No other mitigations are specified.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hgp5-pm7v-q8vg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2024-58363"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a5ba17f44ab8fbf7c789e78
Added to database: 07/18/2026, 15:53:35 UTC
Last enriched: 07/18/2026, 16:23:41 UTC
Last updated: 07/18/2026, 18:37:16 UTC
Views: 13
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.