Security readout for executives and security teams
Plain-English summary
An authenticated SurrealDB user can make the database follow a redirect from a public server to a normally blocked internal address. This server-side request forgery could expose sensitive internal services or let the requester affect their availability or integrity. The supplied assessment is CVSS 4.0 5.8, medium severity.
Executive priority
Prioritize remediation for internet-facing or multi-tenant deployments where less-trusted authenticated users can use HTTP functions. Treat isolated, tightly administered instances as lower urgency after validating permissions and egress controls. Sensitive cloud metadata or administrative services reachable from the database host increase business urgency.
Technical view
SurrealDB versions before 2.2.2 do not revalidate redirect destinations used by HTTP functions against deny-net restrictions. A permitted external URL can therefore redirect the server to a denied IP address. Exploitation requires authentication and a prepared redirect, but no user interaction. The source bundle identifies CWE-918.
Likely exposure
Exposure is most likely where a pre-2.2.2 SurrealDB instance permits authenticated, potentially untrusted users to invoke HTTP functions and can reach sensitive internal endpoints. Risk falls where those functions are unavailable, authorization is tightly restricted, or independent egress controls block internal destinations.
Exploitation context
The source bundle describes a network-reachable attack requiring low privileges and an attacker-controlled redirect. It provides no cited evidence of active exploitation, and the CVE is not listed as KEV. Exploitation status beyond those facts is unknown.
Researcher notes
CVSS 4.0 is 5.8 with AV:N, AC:L, AT:P, PR:L, and UI:N. The primary weakness is redirect destination validation after an initially allowed request. The supplied affected-version entries are ambiguous across 2.0, 2.1, and 2.2 branches; confirm branch-specific fixed versions in the vendor advisory.
Mitigation direction
- Upgrade to SurrealDB 2.2.2 or a later vendor-supported release.
- Consult the vendor advisory for fixed releases applicable to older maintained branches.
- Restrict HTTP-function access to trusted authenticated users until remediation is complete.
- Use independent egress controls to prevent SurrealDB from reaching sensitive internal or metadata endpoints.
- Review internal services reachable from the SurrealDB host and reduce unnecessary access.
Validation and detection
- Inventory SurrealDB versions and identify every instance earlier than 2.2.2.
- Confirm which roles or users can invoke SurrealDB HTTP functions.
- Verify upgraded instances revalidate redirect destinations against deny-net restrictions.
- Review outbound request logs for redirects followed by connections to denied or internal addresses.
- Confirm network controls block unnecessary access from SurrealDB to sensitive internal services.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-71398 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-5q9x-554g-9jgg)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SurrealDB before 2.2.2 SSRF via HTTP Redirect BypassCVE 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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.