CVE-2025-71390 surrealdb CVE debrief

Who should care

Users of SurrealDB versions before 2.2.6, 2.3.6, and 2.1.8 (and 3.0.0-alpha.7 and earlier) should apply patches to prevent potential unauthorized access to restricted internal endpoints. Security teams and administrators responsible for SurrealDB deployments should review the vulnerability and apply necessary mitigations.

Technical summary

SurrealDB fails to validate DNS-resolved hostnames against --deny-net network access restrictions in its http functions. An authenticated user can invoke http functions 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.

Defensive priority

Medium priority due to the potential for unauthorized access to sensitive information and credentials.

Recommended defensive actions

• Apply patches to SurrealDB versions before 2.2.6, 2.3.6, and 2.1.8 (and 3.0.0-alpha.7 and earlier)
• Restrict access to http functions for authenticated users
• Monitor for suspicious activity on internal endpoints
• 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 was published on 2026-07-18T14:17:10.300Z and has not been modified since then. The NVD entry is currently Received. The vulnerability affects SurrealDB versions before 2.2.6, 2.3.6, and 2.1.8 (and 3.0.0-alpha.7 and earlier).

Official resources