CVE-2025-71390 surrealdb CVE debrief

Who should care

Defenders responsible for SurrealDB deployments, particularly those with internal endpoints and sensitive information, should assess exposure and prioritize remediation. This includes verifying and upgrading to patched versions, restricting access to sensitive internal endpoints, and monitoring for suspicious activity. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability and take necessary  

Why it matters

CVE-2025-71390 allows an authenticated user to bypass network access controls in SurrealDB, potentially leading to unauthorized access to sensitive information and internal endpoints. Defenders should prioritize verifying and upgrading to patched versions, restricting access, and monitoring for suspicious activity.

• Potential retrieval or alteration of sensitive information
• Bypass of network access controls
• Increased risk of unauthorized access to internal endpoints
• Need for verification of affected versions and remediation

Technical summary

SurrealDB before 2.2.6, 2.3.6, and 2.1.8 (and 3.0.0-alpha.7 and earlier) fails to validate DNS-resolved hostnames against --deny-net network access restrictions in its http::* functions, allowing an authenticated user to invoke http::<fn>(<url>) with a hostname that resolves to a denied IP address, causing the server to issue the request anyway and return the response. This bypasses network access controls, allowing access to restricted internal endpoints and potentially retrieving or altering sensitive information and credentials, depending on the deployment.

Defensive priority

Defenders should prioritize verifying and upgrading to patched versions of SurrealDB, restricting access to sensitive internal endpoints, and monitoring for suspicious activity.

Recommended defensive actions

• Verify and upgrade to patched versions of SurrealDB (2.2.6, 2.3.6, or 2.1.8, and 3.0.0-alpha.8 or later)
• Restrict access to sensitive internal endpoints
• Monitor for suspicious activity
• Review and update network access controls
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, affected versions, and potential impacts. The vulnerability allows an authenticated user to invoke http::<fn>(<url>) with a hostname that resolves to a denied IP address, causing the server to issue the request anyway and return the response. Defenders should verify affected scope, severity, and vendor guidance, and review compensating controls for exposed systems while remediation is scheduled and verified.

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.