CVE-2024-58363 surrealdb CVE debrief

Who should care

Users of SurrealDB, especially those who rely on database switching and user authentication, should be aware of this vulnerability. Developers and administrators of applications using SurrealDB should assess their exposure and take necessary actions to mitigate the risk.

Technical summary

The vulnerability exists in SurrealDB versions before 1.5.4. When a user switches databases using the USE clause or use method, the system fails to properly validate authentication. This allows an attacker with an authenticated session to impersonate another user in a different database, provided that user has the same identifier. The impact is significant if access control relies solely on the $auth parameter, as it could lead to unauthorized actions.

Defensive priority

Medium priority should be given to patching SurrealDB installations, as the vulnerability can be exploited by authenticated users. Immediate action is recommended for environments where database switching and user impersonation could lead to significant security risks.

Recommended defensive actions

• Patch SurrealDB to version 1.5.4 or later
• Review and update authentication and authorization mechanisms
• Monitor for suspicious database switching activity
• Implement additional access controls beyond $auth parameter if necessary
• Confirm whether affected SurrealDB deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record was published on 2026-07-18T14:17:09.187Z and has not been modified since then. The NVD entry is currently in the 'Received' status. Limited details are available about the specific conditions and potential mitigations beyond patching.

Official resources