Read the docs

MCP session hijack in SurrealDB via shared BoundSubject fingerprint

Priority LOW 37CWE-269Published · Updated

Key facts

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

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-269.

Summary

SurrealDB from 3.1.0 before 3.3.0 uses the access method name instead of per-user identity to bind MCP sessions for JWT and Bearer access, an improper privilege management flaw (CWE-269). An attacker with a valid low-privilege token for the same access method who obtains a victim's mcp-session-id can hijack the session and run MCP tools with the victim's roles and permissions.

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

Description from the CNA

SurrealDB from 3.1.0 before 3.3.0 contains an improper authentication vulnerability where the MCP BoundSubject fingerprint uses the access method name instead of per-user identity for JWT/Bearer access. Attackers with a valid low-privilege token for the same access method and a victim's mcp-session-id can hijack the session and execute MCP tools with the victim's roles and permissions.

Why it matters now

EPSS 0.00319 25th percentileScored 2026-11-07
Fix Fixed surrealdb (surrealdb): 3.3.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

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, which fixes the flaw.

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-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-121419
  2. 2026-11-03 Alias added: GHSA-hprh-85vv-3jpq
  3. 2026-11-05 Priority changed: MEDIUM → LOW

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