CVE-2026-121419

8.1High

Published 03 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite

8.1CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on confidentiality, integrity
Weakness
CWE-269

What an attacker gets

Authenticated attackers can hijack other users' sessions to execute MCP tools with the victim's permissions. This requires the attacker to have a valid low-privilege token for the same access method and the victim's mcp-session-id.

Root cause

The MCP BoundSubject fingerprint incorrectly uses the access method name instead of the unique user identity when validating JWT or Bearer tokens.

Affected versions

SurrealDB versions 3.1.0 through 3.2.x.

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Fix & remediation

Upgrade to SurrealDB 3.3.0 or later. If you cannot upgrade immediately, disable the MCP tool access method until the patch is applied.

remediation — bash
$ surreal version

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-121419