SurrealDB
SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via BoundSubject Collision
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.6high · scored by CNA · CWE-269
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
surrealdb surrealdb
- >= 3.1.0, < 3.3.0
Fixed in 3.3.0
Mitigation
Upgrade surrealdb to 3.3.0 or later.
References
- Vendor advisory github.com/surrealdb/surrealdb/security/adviso…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.