Quick answers
- Is CVE-2026-121419 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121419 being exploited in the wild.
- How severe is CVE-2026-121419?
- High severity, with a CVSS score of 8.1, published 3 November 2026.
- Which products and versions are affected?
- Surrealdb 3.1.0 through 3.2.x before 3.3.0.
- Is there a fix for CVE-2026-121419?
- Yes: fixed in 3.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121419 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121419?
- Check whether you run Surrealdb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.3.0
Technical details
The vulnerability lies in the MCP BoundSubject fingerprint comparison for JWT/Bearer access methods, which uses the access method name instead of per-user identity to identify authenticated sessions. This causes all users of the same access method to produce identical fingerprints regardless of their individual roles. An attacker with a valid token and the victim's mcp-session-id can pass the session re-check and execute MCP tools with the victim's bound permissions.
Affected products
- SurrealDB SurrealDB 3.1.0 through 3.2.x before 3.3.0
Timeline
- 2026-10-19: disclosed
- 2026-11-03: advisory