Read the docs

Server-side request forgery in SurrealDB via JWKS URL default ports

Priority MEDIUM 56CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Information disclosure
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-918 and the CVSS impact.

Summary

SurrealDB from 3.1.0 before 3.3.0 contains a server-side request forgery flaw (CWE-918) in its JWKS URL handling. A database Owner can bypass port-specific deny-net rules by using JWKS URLs with implicit default ports 80 or 443, so blind GET requests reach explicitly denied internal services. The Owner does this by configuring a JWT or record access method whose JWKS URL omits the port.

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

Description from the CNA

SurrealDB from 3.1.0 before 3.3.0 contains a server-side request forgery vulnerability that allows database Owners to bypass port-specific deny-net rules by using JWKS URLs with implicit default ports. Attackers can configure a JWT or record access method whose JWKS URL omits port 80 or 443, causing blind GET requests to explicitly denied internal services.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00246 15th percentileScored 2026-11-07
Fix Fixed surrealdb (surrealdb): 3.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
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.1.0 to before 3.3.03.3.0Patch availableCNA
  • surrealdb Vendorsurrealdb Affected 3.1.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, the fixed version.

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

  • 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-84301 MCP session hijack in SurrealDB via shared BoundSubject fingerprintPriority LOW 37
    • TI-2026-84299 Use-after-free in SurrealDB KV backends via affinitypool spawn_localPriority LOW 37

Timeline

  1. 2026-11-03 Threatist record created from CVE-2026-121422
  2. 2026-11-03 Alias added: GHSA-7wm7-v445-mpw3
  3. 2026-11-07 CISA SSVC decision points changed
  4. 2026-11-07 Priority changed: LOW → MEDIUM

References

  • TI-2026-84300 SurrealDB index planner lets users infer restricted fields CVSS 4.0MEDIUM 5.3
  • 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
  • TI-2025-43508 SurrealDB before 2.2.2 SurrealQL Injection via export CVSS 4.0CRITICAL 9.4
See all 76 →

Sources