<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>SurrealDB (3.1.0 Up To, but Not Including, 3.3.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/surrealdb-3.1.0-up-to-but-not-including-3.3.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 03 Nov 2026 15:59:48 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/surrealdb-3.1.0-up-to-but-not-including-3.3.0/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>SurrealDB: Improper MCP authentication vulnerability (CVE-2026-121419)</title><link>https://feed.craftedsignal.io/briefs/2026-11-surrealdb-auth-bypass/</link><pubDate>Tue, 03 Nov 2026 15:59:48 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-surrealdb-auth-bypass/</guid><description>SurrealDB versions 3.1.0 before 3.3.0 contain an improper authentication vulnerability in the MCP BoundSubject fingerprint.</description><content:encoded>&lt;p>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.&lt;/p>
</content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>