SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via BoundSubject Collision
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| surrealdb | surrealdb | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Surrealdb | Surrealdb |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.319% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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
|