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.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 03 Nov 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via BoundSubject Collision | |
| First Time appeared |
Surrealdb
Surrealdb surrealdb |
|
| Weaknesses | CWE-269 | |
| CPEs | cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Surrealdb
Surrealdb surrealdb |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-03T14:28:16.612Z
Reserved: 2026-11-03T12:29:41.359Z
Link: CVE-2026-121419
No data.
No data.
No data.
OpenCVE Enrichment
No data.
Weaknesses