CVE-2025-71396 surrealdb CVE debrief

Who should care

Defenders responsible for SurrealDB deployments, especially those with scripting enabled, should assess exposure and prioritize verification and remediation efforts. This includes reviewing configurations, verifying versions, and updating to patched versions where necessary. Security teams and operators managing SurrealDB instances should be aware of the potential for resource exhaustion attacks and take proactive measures to mitigate the risk.

Why it matters

CVE-2025-71396 is a denial-of-service vulnerability in SurrealDB that can be exploited by authenticated attackers when scripting is enabled. Defenders should verify versions, configurations, and prioritize updates to prevent potential resource exhaustion attacks.

• Potential resource exhaustion leading to denial of service
• Need to verify SurrealDB versions and configurations
• Possible impact on service availability
• Requires review of scripting configurations and updates

Technical summary

The vulnerability in SurrealDB allows an authenticated attacker to cause a denial of service by submitting long-running JavaScript functions when the scripting capability is enabled. This can lead to resource exhaustion. The issue affects SurrealDB versions before 2.0.5, 2.1.x before 2.1.5, and 2.2.x before 2.2.2. Defenders should verify versions and configurations, especially where scripting is enabled, to prevent potential denial-of-service attacks. The CVE record and NVD entry provide details on the vulnerability, affected versions, and potential impact.

Defensive priority

Defenders should prioritize verifying SurrealDB versions and configurations, especially where scripting is enabled, to prevent potential denial-of-service attacks.

Recommended defensive actions

• Verify SurrealDB versions and configurations to ensure scripting is not enabled unnecessarily.
• Implement monitoring to detect potential resource exhaustion attacks.
• Review and update SurrealDB to versions 2.0.5, 2.1.5, or 2.2.2, or later, as available.
• 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 NVD entry provide details on the vulnerability, affected versions, and potential impact. However, the corpus does not establish evidence of exploitation or specific business impacts.

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.