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… (CVE-2025-71390)
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. An authenticated user can 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.
AI Analysis
Technical Summary
The vulnerability in SurrealDB (CVE-2025-71390) arises from improper validation of DNS-resolved hostnames against the --deny-net network access restrictions in its HTTP functions. Authenticated users can exploit this by supplying a hostname that resolves to an IP address within a denied network range, bypassing the intended network access controls. This results in the server issuing HTTP requests to restricted internal endpoints, potentially exposing or altering sensitive data depending on the deployment context. The affected versions include all releases before 2.2.6, 2.3.6, and 2.1.8, as well as 3.0.0-alpha.7 and earlier.
Potential Impact
An authenticated user can bypass network access restrictions configured in SurrealDB's HTTP functions, allowing unauthorized requests to internal or restricted network endpoints. This can lead to exposure or modification of sensitive information and credentials within the affected environment. The severity is considered moderate based on the potential for unauthorized internal network access and data compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict authenticated user permissions to limit access to HTTP functions or restrict network access at the infrastructure level to mitigate potential exploitation.
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… (CVE-2025-71390)
Description
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. An authenticated user can 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.
CVSS v4.0
Affected software
pkg:github/surrealdb/surrealdbRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in SurrealDB (CVE-2025-71390) arises from improper validation of DNS-resolved hostnames against the --deny-net network access restrictions in its HTTP functions. Authenticated users can exploit this by supplying a hostname that resolves to an IP address within a denied network range, bypassing the intended network access controls. This results in the server issuing HTTP requests to restricted internal endpoints, potentially exposing or altering sensitive data depending on the deployment context. The affected versions include all releases before 2.2.6, 2.3.6, and 2.1.8, as well as 3.0.0-alpha.7 and earlier.
Potential Impact
An authenticated user can bypass network access restrictions configured in SurrealDB's HTTP functions, allowing unauthorized requests to internal or restricted network endpoints. This can lead to exposure or modification of sensitive information and credentials within the affected environment. The severity is considered moderate based on the potential for unauthorized internal network access and data compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict authenticated user permissions to limit access to HTTP functions or restrict network access at the infrastructure level to mitigate potential exploitation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vp9r-94xg-q7q8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-71390"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a5ba17e44ab8fbf7c789b82
Added to database: 07/18/2026, 15:53:34 UTC
Last enriched: 07/18/2026, 16:21:47 UTC
Last updated: 07/18/2026, 20:17:54 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.