CVE-2026-63745 surrealdb CVE debrief

Who should care

Users of SurrealDB versions before 3.1.0 should apply patches or mitigations to prevent potential unauthorized access. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure the security of their systems.

Technical summary

The vulnerability allows authenticated users to spoof composite record-id field values by writing to editable body fields. This can lead to bypassing permission rules that gate access on id components like tenant isolation. The CVSS score of 5.3 indicates a Medium severity vulnerability. The vulnerability affects SurrealDB versions before 3.1.0. To address this vulnerability, users should focus on upgrading to version 3.1.0 or later, and implement additional security measures such as monitoring and restricting access to sensitive data. It is also crucial to conduct inventory checks to identify and remediate vulnerable systems, review relevant monitoring, detection, and logs for exposed assets that need extra review, and track exceptions, retest remediated assets, and close the item only after evidence is documented. Furthermore, confirming whether affected product deployments exist in managed environments and assigning an owner for follow-up is essential. The CVE record was published on 2026-07-20T12:19:44.003Z and was last modified on 2026-07-21T18:37:56.803Z. The NVD entry is currently Awaiting Analysis.

Defensive priority

Medium priority due to the CVSS score of 5.3 and the potential for unauthorized access.

Recommended defensive actions

• Apply patches or updates to SurrealDB version 3.1.0 or later
• Implement compensating controls to monitor and restrict access to sensitive data
• Conduct inventory checks to identify and remediate vulnerable systems
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record was published on 2026-07-20T12:19:44.003Z and was last modified on 2026-07-21T18:37:56.803Z. The NVD entry is currently Awaiting Analysis. This information is based on the provided source corpus. Further verification is recommended to confirm affected scope and severity.

Official resources