CVE-2026-109335 surrealdb CVE debrief

Who should care

Defenders responsible for SurrealDB deployments should assess exposure to this vulnerability and take steps to restrict access to sensitive data. This includes verifying SurrealDB versions in use, reviewing COMPUTED field usage, and implementing necessary controls to prevent unauthorized data access. Additionally, security teams and vulnerability management teams should prioritize verifying versions and assessing exposure to this vulnerability.

Why it matters

CVE-2026-109335 is a high-severity information disclosure vulnerability in SurrealDB versions 3.0.0 before 3.3.0. Defenders should prioritize verifying versions, assessing exposure, and restricting access to sensitive data through COMPUTED fields.

• Defenders need to verify SurrealDB versions and COMPUTED field usage to restrict access to sensitive data.
• Exposure to this vulnerability could allow unauthorized data access.
• Defensive priority is high due to potential for data disclosure.

Technical summary

The vulnerability allows users to read values hidden by field-level SELECT permissions through COMPUTED fields. Attackers can select records whose readable COMPUTED fields derive from hidden fields or use write RETURN clauses with $before/$after to expose hidden values. This information disclosure vulnerability affects SurrealDB versions 3.0.0 before 3.3.0, and defenders should prioritize verifying versions and assessing exposure to this vulnerability. This involves checking if any COMPUTED fields are being used to derive values from hidden fields and taking steps to restrict access to sensitive data.

Defensive priority

Defenders should prioritize verifying the versions of SurrealDB in use and assessing exposure to this vulnerability. This involves checking if any COMPUTED fields are being used to derive values from hidden fields and taking steps to restrict access to sensitive data.

Recommended defensive actions

• Verify SurrealDB versions in use and assess exposure to CVE-2026-109335
• Restrict access to sensitive data through COMPUTED fields
• Monitor for potential exploitation attempts
• 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 CVE record and source item provide details on the vulnerability, including its description and affected versions. However, there is limited information on the exploitation of this vulnerability in the wild.

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.