CVE-2026-109334 surrealdb CVE debrief

Who should care

Defenders who manage SurrealDB instances should assess their exposure and prioritize patching to version 3.3.0 or later. This includes reviewing compensating controls for exposed systems, monitoring for suspicious activity, and verifying the authenticity of requests and responses. Additionally, defenders should track exceptions, retest remediated assets, and close the item only after evidence is documented.

Why it matters

CVE-2026-109334 is a high-severity vulnerability in SurrealDB before version 3.3.0, allowing cross-tenant access via Surreal-NS/Surreal-DB headers and RPC use. Defenders should prioritize patching and verifying request authenticity.

• An authenticated attacker can read, create, modify, and delete rows in another tenant.
• An authenticated attacker can read DEFINE PARAM values in another tenant.
• Defenders need to verify the authenticity of requests and responses to prevent exploitation.
• Patching to version 3.3.0 or later is required to fix the vulnerability.

Technical summary

The vulnerability is caused by a lack of checks on the caller-selected namespace or database against the level at which a namespace- or database-level system user authenticated. This allows an authenticated attacker to access data from another tenant where table PERMISSIONS allow it. The vulnerability has a CVSS score of 8.6 and is considered HIGH severity. An attacker can exploit this vulnerability to read, create, modify, and delete rows and read DEFINE PARAM values in another tenant. Defenders should prioritize patching SurrealDB instances to version 3.3.0 or later, and verify the authenticity of requests and responses.

Defensive priority

Defenders should prioritize patching SurrealDB instances to version 3.3.0 or later, and verify the authenticity of requests and responses.

Recommended defensive actions

• Patch SurrealDB instances to version 3.3.0 or later
• Verify the authenticity of requests and responses
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check 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

Evidence notes

The vulnerability is caused by a lack of checks on the caller-selected namespace or database against the level at which a namespace- or database-level system user authenticated. This allows an authenticated attacker to access data from another tenant.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.