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 versions before 2.2.6, 2.3.6, 2.1.8, and version 3.0.0-alpha.7 and earlier contain a vulnerability where DNS-resolved hostnames are not properly validated against --deny-net network access restrictions in the http::* functions. This allows an authenticated user to bypass network access controls by invoking HTTP functions with hostnames that resolve to denied IP addresses, potentially accessing restricted internal endpoints and sensitive information.
AI Analysis
Technical Summary
SurrealDB before versions 2.2.6, 2.3.6, 2.1.8, and 3.0.0-alpha.7 and earlier fails to validate DNS-resolved hostnames against the --deny-net network access restrictions in its http::* functions. An authenticated user can exploit this by invoking http::<fn>(<url>) with a hostname that resolves to an IP address within a denied network range. The server issues the request regardless of the deny-net restrictions and returns the response, effectively bypassing network access controls. This can lead to unauthorized access to internal endpoints and may result in retrieval or alteration of sensitive data and credentials depending on the deployment environment.
Potential Impact
The vulnerability allows authenticated users to bypass network access restrictions configured via --deny-net, enabling them to access internal or restricted network resources that should be blocked. This can lead to unauthorized disclosure or modification of sensitive information and credentials, posing a significant security risk to affected deployments.
Mitigation Recommendations
No official patch links are provided in the data, and patch status is not explicitly confirmed. Therefore, patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict authenticated user permissions to trusted users only and monitor usage of http::* functions to detect potential abuse.
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 versions before 2.2.6, 2.3.6, 2.1.8, and version 3.0.0-alpha.7 and earlier contain a vulnerability where DNS-resolved hostnames are not properly validated against --deny-net network access restrictions in the http::* functions. This allows an authenticated user to bypass network access controls by invoking HTTP functions with hostnames that resolve to denied IP addresses, potentially accessing restricted internal endpoints and sensitive information.
CVSS v3.1
Score 8.8high
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
SurrealDB before versions 2.2.6, 2.3.6, 2.1.8, and 3.0.0-alpha.7 and earlier fails to validate DNS-resolved hostnames against the --deny-net network access restrictions in its http::* functions. An authenticated user can exploit this by invoking http::<fn>(<url>) with a hostname that resolves to an IP address within a denied network range. The server issues the request regardless of the deny-net restrictions and returns the response, effectively bypassing network access controls. This can lead to unauthorized access to internal endpoints and may result in retrieval or alteration of sensitive data and credentials depending on the deployment environment.
Potential Impact
The vulnerability allows authenticated users to bypass network access restrictions configured via --deny-net, enabling them to access internal or restricted network resources that should be blocked. This can lead to unauthorized disclosure or modification of sensitive information and credentials, posing a significant security risk to affected deployments.
Mitigation Recommendations
No official patch links are provided in the data, and patch status is not explicitly confirmed. Therefore, patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict authenticated user permissions to trusted users only and monitor usage of http::* functions to detect potential abuse.
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: 08/13/2026, 19:14:26 UTC
Last updated: 08/27/2026, 22:52:08 UTC
Views: 117
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.