SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via BoundSubject Collision

Summary

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.

Remediation

1. Inventory every surrealdb surrealdb deployment, including staging.
2. Upgrade surrealdb surrealdb to 3.3.0.
3. Confirm the running version after the upgrade.

References

• Advisoryhttps://github.com/surrealdb/surrealdb/security/advisories/GHSA-pgh9-49q4-hqcx
• Advisoryhttps://www.vulncheck.com/advisories/surrealdb-3.1.0-before-3.3.0-mcp-session-hijack-via-boundsubject-collision