Security readout for executives and security teams
Plain-English summary
An authenticated SurrealDB user may bypass configured network restrictions by using a hostname that resolves to a blocked IP address. The database could then reach internal services and return their responses. Business impact depends on accessible endpoints, potentially exposing sensitive information, credentials, or operations that alter internal systems.
Executive priority
Prioritize remediation for internet-facing or multi-tenant deployments and environments where lower-trust users can execute http::* functions. Treat instances reaching cloud metadata, credential stores, or administrative services as urgent. Other affected instances should enter the normal patch cycle after exposure is confirmed.
Technical view
Affected SurrealDB http::* functions check the supplied hostname but fail to revalidate its DNS-resolved IP against --deny-net restrictions. Exploitation requires authentication and a suitable hostname, but no user interaction. CVSS 4.0 is 5.8; downstream confidentiality, integrity, and availability impacts may be high where sensitive internal endpoints are reachable.
Likely exposure
Exposure is most likely where affected SurrealDB versions permit authenticated users to invoke http::* functions, enforce --deny-net, and have network access to sensitive internal services. Deployments without those conditions are less exposed. The supplied version information identifies affected branches before 2.1.8, 2.2.6, and 2.3.6, plus 3.0.0-alpha.7 and earlier.
Exploitation context
The bypass is remotely triggerable by a low-privileged authenticated user, with a preparatory DNS condition. It may enable server-side access to otherwise denied internal addresses. The bundle reports no CISA KEV listing and provides no evidence of active exploitation, public exploit availability, or observed attacks.
Researcher notes
This is an authorization-policy bypass caused by incomplete validation after DNS resolution, mapped to CWE-863. The supplied CVSS vector includes low privileges, no user interaction, and a preparatory condition. Exact exploitability and impact are deployment-specific. The bundle does not establish whether DNS rebinding is required, identify indicators of compromise, or document exploitation in the wild.
Mitigation direction
- Upgrade each affected stable branch to 2.1.8, 2.2.6, 2.3.6, or a later vendor-supported release.
- For affected 3.0.0 alpha deployments, consult the vendor advisory for an appropriate safe release.
- Restrict permission to invoke http::* functions to users with a documented operational need.
- Limit SurrealDB outbound connectivity to required destinations using independent network controls.
- Protect internal metadata, credential, and administrative endpoints from SurrealDB network access.
Validation and detection
- Inventory SurrealDB versions and identify deployments within the affected release ranges.
- Confirm whether --deny-net is configured and whether security decisions rely on it.
- Review which authenticated roles can invoke http::* functions.
- Map outbound reachability from SurrealDB to internal, metadata, credential, and administrative services.
- Review request and network logs for unexpected hostname-based access to denied internal address ranges.
- After upgrading, verify the installed version and confirm denied destinations remain unreachable after DNS resolution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-71390 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.8MediumVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-m3c3-78fh-w3w7)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SurrealDB before 2.3.6 deny-net Bypass via DNS ResolutionCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.