Evidence · DiggingBeagle record
SurrealDB GHSA-pgh9-49q4-hqcx: MCP session authorization collision
The October 19, 2026 maintainer advisory describes an MCP HTTP session-fingerprint collision between different JWT users sharing an access-method name. A valid lower-privilege token plus a known victim session ID were used in the disclosed reproduction. Metadata lists affected versions from 3.1.0, while narrative identifies MCP HTTP from 3.2.0; 3.3.0 is listed as patched.
- Published
- Oct 19, 2026
- Source role
- primary disclosure
Evidence record
The October 19, 2026 maintainer advisory describes an MCP HTTP session-fingerprint collision between different JWT users sharing an access-method name. A valid lower-privilege token plus a known victim session ID were used in the disclosed reproduction. Metadata lists affected versions from 3.1.0, while narrative identifies MCP HTTP from 3.2.0; 3.3.0 is listed as patched.
Claim-level citations (3)
- supportsSurrealDB MCP sessions could inherit another user’s authorization context: SurrealDB documents an MCP session-fingerprint collision when different JWT users share an access-method name in affected configurations.
Security advisory, vulnerability details
- supportsSurrealDB MCP sessions could inherit another user’s authorization context: The vendor lists SurrealDB 3.3.0 as a fixed version.
Security advisory, patched versions
- supportsSurrealDB MCP sessions could inherit another user’s authorization context: The October 19 advisory specifies an affected package range beginning at 3.1.0, but its narrative describes affected MCP HTTP transport from 3.2.0; it reports reproducing seven of seven checks on a released 3.2.0 binary.
GitHub advisory metadata, Affected versions, Description, reproduced binaries