Read the docs

SSRF guard bypass in SurrealDB via IPv6 transition addresses

Priority LOW 21CWE-918Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

SurrealDB from 3.2.0 before 3.3.0 contains a server-side request forgery flaw in the FilteringResolver is_private_ip check, which fails to unwrap NAT64, 6to4, and Teredo IPv6 addresses (CWE-918). An authenticated user who triggers outbound HTTP requests through SurrealQL http functions can use these transition addresses to embed private IPv4 targets and reach localhost, internal services, or cloud metadata endpoints.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

SurrealDB from 3.2.0 before 3.3.0 contains a server-side request forgery vulnerability in the FilteringResolver is_private_ip check that fails to unwrap NAT64, 6to4, and Teredo IPv6 addresses. Authenticated users triggering outbound HTTP requests via SurrealQL http functions can use transition addresses embedding private IPv4 targets to reach localhost, internal services, or cloud metadata endpoints.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00163 5th percentileScored 2026-11-07
Fix Fixed surrealdb (surrealdb): 3.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
surrealdbsurrealdb3.2.0 to before 3.3.03.3.0Patch availableCNA
  • surrealdb Vendorsurrealdb Affected 3.2.0 to before 3.3.0 Fixed in 3.3.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*——surrealdb
  • cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:* Versions — — ·surrealdb

Remediation

Upgrade SurrealDB to version 3.3.0 or later, which fixes the issue in the surrealdb package.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

  • Fix · CNA surrealdb (surrealdb) Fixed in 3.3.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    surrealdb 3.3.0

    7 records Highest priority Priority MEDIUM 2 MEDIUM, 5 LOW

    Other records, highest priority first

    • TI-2026-84300 SurrealDB index planner lets users infer restricted fieldsPriority MEDIUM 57
    • TI-2026-84304 Server-side request forgery in SurrealDB via JWKS URL default portsPriority MEDIUM 56
    • TI-2026-84301 MCP session hijack in SurrealDB via shared BoundSubject fingerprintPriority LOW 37

Timeline

  1. 2026-11-03 Threatist record created from CVE-2026-121420
  2. 2026-11-03 Alias added: GHSA-3rgm-63j6-74qx
  3. 2026-11-03 CISA SSVC decision points changed

References

  • TI-2026-84300 SurrealDB index planner lets users infer restricted fields CVSS 4.0MEDIUM 5.3
  • TI-2026-84304 Server-side request forgery in SurrealDB via JWKS URL default ports CVSS 4.0MEDIUM 5.1
  • TI-2026-45344 SurrealDB before 3.1.0 Session Hijacking via /rpc sessions CVSS 4.0HIGH 8.7
  • TI-2024-38452 SurrealDB before 1.1.0 Denial of Service via HTTP Headers CVSS 4.0HIGH 8.7
  • TI-2026-45347 SurrealDB before 3.1.0 Denial of Service via JSON Parser CVSS 4.0HIGH 8.7
  • TI-2026-45334 SurrealDB before 3.1.0 Denial of Service via malformed RPC use CVSS 4.0HIGH 8.7
See all 76 →

Sources