Skip to content
Fencer Intel
high 8.8

CVE-2025-71390 json

SurrealDB before 2.3.6 deny-net Bypass via DNS Resolution

published 3mo ago modified last mo. also GHSA-m3c3-78fh-w3w7 , EUVD-2025-210490

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

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. 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.

Patch / fix

  • crates.io SurrealDB 2.1.8, 2.2.6, 2.3.6, 3.0.0-alpha.7
  • surrealdb surrealdb 2.2.6, 2.3.6

Is CVE-2025-71390 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 5.8 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 4.0 5.8 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
crates.io SurrealDB
>=2.1.0, <2.1.8
>=2.2.0, <2.2.6
>=3.0.0-alpha.1, <3.0.0-alpha.7
>=2.3.0, <2.3.6
2.1.8
2.2.6
3.0.0-alpha.7
2.3.6

Affected products

  • surrealdb surrealdb

Classification

Weakness
  • CWE-863 Incorrect Authorization
  • CWE-923 Improper Restriction of Communication Channel to Intended Endpoints

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.